Further we added an option, to remove the “c: users” directory when shipping an app. Twitch app for mac. Wine will automatically add new users, when the app is run on a clients Mac. Then you can automatically remove installer files (.msi) from your prefix before shipping – if they are no longer needed. Lastly, we have optimized how WineBottler runs your prefixes. Is it safe to use 'WINE' on a Mac? I downloaded and installed the WINE version for Mac (www.winehq.org, don't remember exactly where I downloaded it). I was wondering, though, that if I get a Windows virus, would it be likely run on my Mac through WINE?

Winecfg (Wine configuration) (1,620) Initial release 4 July 1993; 25 years ago ( 1993-07-04) 3.0.4 (November 29, 2018; 29 days ago ( 2018-11-29)) 4.0-rc4 (December 28, 2018; 0 days ago ( 2018-12-28)) Written in,,, • • (development) • (experimental),, 21 MB (compressed tar.) Available in English v2.1+ Website Wine ( for Wine Is Not an ) is a that aims to allow ( and ) developed for to run on. Wine also provides a, known as Winelib, against which developers can Windows applications to help them to Unix-like systems. Wine the Windows by translating Windows into -compliant, recreating the of Windows systems, and providing alternative implementations of Windows, system services through wineserver and various other components (such as, the, and ). Wine is predominantly written using reverse-engineering, to avoid issues.

The name Wine was initially an abbreviation for Windows Emulator. Wine later shifted to the Wine Is Not an Emulator in order to differentiate the software from. No or occurs when running a Windows under Wine. 'Emulation' would refer to of code intended for one (such as ) by software running on a different processor (such as ). While the name sometimes appears in the forms WINE and wine, the project developers have agreed to standardize on the form Wine. Wine is primarily developed for Linux and, they are (As of November 2018 ) well maintained and packages are available for them. In a 2007 survey by desktoplinux.com of 38,500 Linux desktop users, 31.5% of respondents reported using Wine to run Windows applications.

This plurality was larger than all programs combined, as well as larger than the 27.9% who reported not running Windows applications. Bob Amstadt, the initial project leader, and Eric Youngdale started the Wine project in 1993 as a way to run Windows applications on. It was inspired by two ' products, the for the operating system, and the, which was an attempt to get the fully reimplemented in the public domain as an standard but rejected due to pressure from in 1996. Wine originally targeted for, but as of 2010 focuses on and versions which have become the standard on newer operating systems. The project originated in discussions on in in June 1993. Has led the project since 1994.

The project has proven time-consuming and difficult for the developers, mostly because of incomplete and incorrect of the Windows API. While Microsoft extensively documents most Win32, some areas such as and have no publicly available specification from Microsoft, and Windows also includes undocumented low-level functions, undocumented behavior and obscure that Wine must duplicate precisely in order to allow some applications to work properly. Consequently, the Wine team has many function calls and file formats in such areas as.

[ ] The Wine project originally released Wine under the same as the X Window System, but owing to concern about versions of Wine not contributing their changes back to the core project, work as of March 2002 has used the LGPL for its licensing. Wine officially entered beta with version 0.9 on 25 October 2005. Version 1.0 was released on 17 June 2008, after 15 years of development.

Version 1.2 was released on 16 July 2010, version 1.4 on 7 March 2012, version 1.6 on 18 July 2013. And version 1.8 on 19 December 2015. Development versions are released roughly every two weeks. Corporate sponsorship [ ] The main corporate sponsor of Wine is, which employs Julliard and many other Wine developers to work on Wine and on, CodeWeavers' supported version of Wine. CrossOver includes some application-specific tweaks not considered suitable for the WineHQ [ ] version, as well as some additional proprietary components.

The involvement of for a time assisted the project, chiefly by employing Julliard and others to work on it. Corel had an interest in porting, its, to Linux (especially ). Corel later cancelled all Linux-related projects after Microsoft made major investments in Corel, stopping their Wine effort. Other corporate sponsors include, which hired CodeWeavers to fix Wine so ran well enough to be ported directly to Linux using the same binary as on Windows; Google later paid for improvements to Wine's support for. Wine is also a regular beneficiary of Google's program. Software architecture [ ] The goal of Wine is to implement the fully or partially that are required by programs that the users of Wine wish to run on top of a Unix-like system. Win32 API [ ] The Win32 function calls (over 10,000 library calls) are collectively called the Win32 API.