It works with the following versions of OS X. OS X 10.6 (Snow Leopard) OS X 10.7 (Lion) OS X 10.8 (Mountain Lion) OS X 10.9 (Mavericks) It’s a quick download with nothing to unpack or install. Simply run the Wineskin.app file when it finishes downloading. Installing Wine and the Wrapper. You then need to go back to Wineskin and configure some screen settings. Go to the Wineskin menu and Click on Set Screen Options and uncheck the option “Decorate Windows” and click Done. If you’re using macOS 10.12 Sierra or 10.13 High Sierra, it’s very important that you also uncheck the box “Auto Detect GPU Info for Direct3D”.
Translations of this page:Français (Translators, please see Discussion page.)
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.
Prerequisites:
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. 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.
Winehq packages can be installed using homebrew
XQuartz can be installed using;
To install wine the following command can be used;
wine-stable, wine-devel or wine-staging packages can be installed using the above example.The advantage of installing via homebrew means wine is available from a standard terminal sessionThe --no-quarantine line to used to above brew adding the quarantine bit
See Building Wine on macOS
Using Homebrew:
Using MacPorts, uninstall the wine package you previously installed:
Replace wine with wine-devel 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:
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 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.