Difference between revisions of "MacOS"

From WineHQ Wiki
Jump to: navigation, search
(Building Wine)
(Building Wine)
Line 23: Line 23:
== Building Wine ==
== Building Wine ==
[http://brew.sh Homebrew], [http://www.macports.org MacPorts], and [http://www.finkproject.org Fink] are source repositories that can make it easier to build WINE on macOS.
Note, however, that they are not part of the Wine Project and not supported here; any problems with Homebrew, Macports, or Fink builds should be reported to the respective site.
See [[macOS/Building|Building Wine on macOS]]
See [[macOS/Building|Building Wine on macOS]]

Latest revision as of 17:28, 7 February 2017

Translations of this page (incomplete): not yet ported. Translators, please see Discussion page.

Installing WineHQ packages

Official WineHQ packages of the development and staging branches are available for macOS 10.8 and higher. Please test these packages and report any bugs at http://bugs.winehq.org.


  1. XQuartz >= 2.7.7
  2. Gatekeeper must not be set to block unsigned packages.


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.

Building Wine

See Building Wine on macOS

Uninstalling Wine

  • Remove the source tree and binaries.

Using Homebrew:

brew rm wine && brew rm $(join <(brew leaves) <(brew deps wine))

Using MacPorts, uninstall the wine package you previously installed:

sudo port uninstall --follow-dependencies wine

Replace wine with wine-devel if you installed the development version.

Using Fink:

fink remove wine

Replace wine with wine-dev if you installed the development version.

Otherwise and if you used `sudo make install`, revert it:

sudo make uninstall

Then simply delete your local Wine source code directory:

rm -rf src/wine
  • Clean-up pseudo C: drive and registry entries as well as all programs installed to C:
rm -rf $HOME/.wine
  • 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.
rm -rf $HOME/.local

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.

See Also