Translations of this page:Français (Translators, please see Discussion page.)
Installing WineHQ packages
Official WineHQ packages of the development and stable branches are available for macOS 10.8 to 10.14 (Wine won't work on macOS Catalina 10.15). Please test these packages and report any bugs at http://bugs.winehq.org.
- The next version, CrossOver Mac 17, is due to be released this autumn and will be built on Wine 2.8, will be compatible with macOS 10.13 (High Sierra) and will support Microsoft Office 2016 (which.
- Wine 3.0 for Mac is available as a free download on our application library. The current setup file available for download requires 108.9 MB of hard disk space. The unique identifier for this application's bundle is org.kronenberg.Wine.
- Wine Source Downloads. WineHQ download server - our official source release site. Git - instructions for building Wine from git. Ibiblio.org - alternative download site for the official source and documentation tarballs. See Building Wine for help on configuring and building Wine. Wine-staging GitHub repository.
- How to: Install Wine on Mac OS X. Mac OS X could be the best operating system ever but there's still one thing that it lacks: you can neither run any essential Windows apps, nor even install Wine to make it possible.
- You'll see Wine.app Downloads if you scroll down that page past WineBottler. Choose the version most compatible with your macOS system. The way it works is simple: Double-click a Windows.EXE and macOS attempts to open it inside the Wine.app. If that fails, then try WineBottler, which is more convoluted to use.
Afterwards, empty the Trash to delete Wine traces and them reboot your Mac. So that’s how you can delete Wine and its leftovers manually. If you are unfamiliar with the operations or if you want to save some trouble in this task, we suggest you to adopt the next solution, to easily and completely uninstall Wine and WineBottler. What is Wine? Wine (originally an acronym for 'Wine Is Not an Emulator') is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems, such as Linux, macOS, & BSD.
Prerequisites:
- XQuartz >= 2.7.7
- Gatekeeper must not be set to block unsigned packages.
Installing:
Both .pkg files and tarball archives are available at https://dl.winehq.org/wine-builds/macosx/download.html.
Installing from a .pkg file is recommended for inexperienced users.
To install from a .pkg file, double-click on the package, and the usual macOS installer wizard should open. The process should be self-explanatory. It is possible to install the package either for all users (needs administrator privileges), or just for your current user. After the installation is finished, you should find an entry 'Wine Staging' or 'Wine Devel' in your Launchpad. By clicking on it, a new Terminal window opens with a short introduction into some important wine commands. Dmg consulting group. You can now directly start wine/winecfg/.. from the Terminal, as the PATH variable is set correctly. For user convenience, the package also associates itself with all *.exe files, which means you can run windows executables just by double-clicking on them.
To install from a tarball archive, simply unpack it into any directory. There is no need to set DYLD_* environment variables; all paths are relative, so it should work as long as the directory structure is preserved (you can skip the /usr prefix though using --strip-components 1).
For more information, see https://www.winehq.org/pipermail/wine-devel/2015-December/110990.html and https://www.winehq.org/pipermail/wine-devel/2016-January/111010.html.
Building Wine
See Building Wine on macOS
Uninstalling Wine
- Remove the source tree and binaries.
Using Homebrew:
Using MacPorts, uninstall the wine package you previously installed:
Replace wine with wine-devel if you installed the development version.
Using Fink:
Replace wine with wine-dev if you installed the development version.
Otherwise and if you used `sudo make install`, revert it:
Then simply delete your local Wine source code directory:
- Clean-up pseudo C: drive and registry entries as well as all programs installed to C:
- Check the hidden directory `$HOME/.local/` where Wine stores some desktop menu entries and icon files as it interoperates with the X.Org Foundation and the Free Desktop.
Note: Files in this directory are unused on macOS unless you use a UNIX window manager and other X11 applications instead of the native MacOS apps.
Third Party Versions
Third party versions of Wine, such as Wineskin, Winebottler, and PlayOnMac, are not supported by WineHQ. If you are using one of those products, please retest in plain Wine before filing bugs, submitting AppDB test reports, or asking for help on the forum or in IRC.