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.
Prerequisites:
- Now, Install any windows application to run with Wine on your Linux OS; After installation, open the terminal and Type the name of the application. For example, if you download a file named “itunesinstaller.exe”, “then type Wine itunesinstaller.exe” on terminal and press Enter.
- Brew cask install (selected wine package) 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 session Building Wine. See Building Wine on macOS. Uninstalling Wine. Remove the source tree and binaries. Using Homebrew.
Jan 23, 2020 Wine allows OS X users to run Windows applications. Note: this listing is for the official release of Wine, which only provides source code. If you want a version of Wine that is packaged specifically for OS X, then use Winebottler, available here. Wine (originally an acronym for 'Wine Is Not an Emulator') is a compatibility layer capable of running Windows applications on several POSIX. May 27, 2019 install xquartz is self-explanatory, meaning that you are installing the xquartz program on your Mac; Once the installation is complete, Terminal will pause and then wait for your next command, i.e. The next step. Step 3: Wine Installation. Now that we have everything ready, all we have to do is install Wine on Mac. Homebrew will install it for. May 27, 2019 Wine is a pretty old application, first launched in 1993. It is completely free as well as legal. Even though Boot Camp is available, which allows you to install Windows on a Mac, you are required to boot up every time you want to run Windows. Wine helps you cut to the chase and run a Windows program directly.
- 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. 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.
Installing Winehq packages using homebrew
Winehq packages can be installed using homebrew
![Installer Wine Mac Installer Wine Mac](/uploads/1/2/6/3/126378259/516551649.jpg)
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 session
Building Wine
See Building Wine on macOS
Uninstalling Wine
- Remove the source tree and binaries.
Install Wine Mac Brew
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.
See Also
Retrieved from 'https://wiki.winehq.org/index.php?title=MacOS&oldid=3537'
With 32-bit program support going away on the Mac with Catalina we need to start seriously figuring out how to have WINE run on these newer systems so that reasonable instructions can be provided.Right now we can use VMs (VirtualBox, Parallels, VM Fusion) using other operating systems (Ubuntu, Red Hat, or if you can actually get it to work an older version of the MacOS) thought doing this correctly is kind of 'uhhh, how do you do that?'
But is that the best (ie easiest) solution we can come up with or is there some other method on the table we could use?