- 2Preliminaries
- 3Dependencies
Building Wine on macOS
If you just want to install a recent version of Wine, and possibly report Bugs or AppDB tests, you should be fine just following the instructions on the main macOS page for installing a WineHQ package.
If you're interested in Submitting Patches or Regression Testing though, you'll want to build Wine from the tip of WineHQ's Git repo; this page explains how to do that on macOS in more detail.
Wine for mac free download. Wine Wine is an Open Source implementation of the Windows API on top of X and Unix. Wine provides both a. Jun 24, 2018 Published on Jun 24, 2018. To run.exe files on Mac you need to use Wine or Winebottler. Wine will let you run the exe directly, whereas Wine bottler will package the.exe into a macOS app that.
Homebrew, MacPorts, and Fink are source repositories that can make it easier to build WINE on macOS, and some notes on using them are provided below. Note, however, that they are not part of the Wine Project; any problems with Homebrew, Macports, or Fink should be reported to the respective site.
In order to build and run Wine, you might need to install some extra software. Getting it shouldn't be much trouble though.
Xcode
The Xcode development suite is the primary kit you will need, regardless of whether you decide to do a minimal build from git, use a build script, or download from one of the ports projects. A version of it will be included in the Optional Installs folder of your macOS installation DVD. You should also be able to download the latest version for your model from the Apple developer site.
Note: If you don't want to install the full suite, you should be able to make due with just the Command-Line Tools component of Xcode. This will include all of the necessary build tools and even git. Any other libraries should come pre-installed in macOS or can be pulled in automatically by other tools.
XQuartz
In the past, Wine's native Mac driver still needed a good deal of work so running Wine on macOS required installing an X11 server too. This is no longer necessary, but there are still some features missing from the Mac driver (see the to-dos on the macOS page) so you still might want to run Wine with the X11 driver.
According to Wikipedia, from v10.3 (Panther) to v10.7 (Lion) of macOS, Apple at least included a Mac-compatible X11 server as an optional install. However, since v10.8 (Mountain Lion), Apple has stopped providing its own release of the X11 server and advises all users to download the newest version of a compatible X11 server directly from upstream.
The open-source XQuartz project develops the Mac version of X11; you can download the disk-image file directly from there, then just use the macOS installer.
During setup, the upstream XQuartz disk-image will replace /usr/X11 (which is in most PATH variables) with a symlink to /opt/X11 (where it installs the files). However, if you upgrade your release of macOS, this symlink may get clobbered, leading to fatal errors in X11 programs. Reinstalling XQuartz will repair the link automatically, or you can manually restore it with:
If you have a supplementary package manager, you might also be able to grab XQuartz (or an equivalent port of the vanilla xorg server):
- On homebrew, you can grab XQuartz from the related Caskroom repo:
- On MacPorts, you can get fresh ports of either the xorg-server (stable X11 server), xorg-server-devel (development X11 server), or xorg (full X11 system) packages. For example:
Once you have Xcode and a version of the X11 server (not required but highly recommended), you need to grab both the build and runtime dependencies for Wine. While you can just run Wine's configure script and keep installing libraries that it complains are missing, using a package manager will save you a lot of trouble and keep your system cleaner.
The main caveat with the various macOS package repos is that you do not want to mix them. Once you've decided to use one, stick with it, and if you decide to switch to a different one, it's probably best to uninstall all of your old packages first, then reinstall them with the new system.
The subsections below describe ways you can get just the necessary dependencies for Wine. If you want, you can always just install the appropriate wine package, which will pull in all the other packages you need. At that point, you can either uninstall just the wine package, or keep it and run your own build from within its directory.
Homebrew
Homebrew no longer provides a wine formula instead using cask to install wine.
The following would cover basic requirements;
As homebrew no longer provides universal dylibs anything outside of XQuartz provided files and the basic build dependencies would need to be built from source
MacPorts
On MacPorts, to get all the dependencies for Wine, both build and runtime, you just want to use the rdepof: query (short for 'recursive depends of') with the install command. Unless you definitely want the stable release of Wine, use the wine-devel package to get the most up-to-date dependency list:
Please Note:
If you're running macOS High Sierra you need to install XCode 9 & XCode 9 Command Line Tools, not the versions from the App Store.
If your running macOS Mojave you need to do some workarounds check https://trac.macports.org/ticket/56991#comment:70
Now with the dependencies installed, you will use almost the same procedure as described on the Building Wine page. You should be able to run ./configure and make with the same parameters as on another system.
Note: In the past on macOS, it was necessary to point to libraries and headers installed through the package managers too. However, recent versions of all the major package managers should either automatically add to your PATH variable or create symlinks into /usr/local.
You can configure your build directory to compile with clang like so:
Please Note: While Wine can be compiled using XCode on macOS (Compiling with XCode10 requires MacOSX10.13.sdk & setting min version to 10.7) , however compiling wine64 will have problems with regedit and other components so its better to cross-compile using Docker (instructions for this will be added later)
When installing Wine from source on macOS, you may need to make some quick configuration changes.
After compiling Wine from source, you can install it into /usr/local with make install, but it's highly recommended that you run it from the build directory.
Depending on how you installed XQuartz, you might see fatal errors in X11 when you try to run your own build of wine from the command-line. This is due to XQuartz installing into the /opt/X11/ directory and creating symlinks to /usr/X11/, neither of which is typically checked by the macOS dynamic linker. There are a couple of workarounds for this:
- The first is to add the usr/X11/lib directory to the DYLD_FALLBACK_LIBRARY_PATH environment variable. You can do this when invoking wine like so:
- The other method is to create symlinks to the libraries in usr/X11/lib/ from inside /usr/local/lib:
However, this second approach is more tedious to undo and may be more fragile in some situations.
You might need to tweak the actual directories in your list, but you can avoid the tedium of typing the list every time by setting it in one of your shell config files (e.g. .profile, .bash_profile, or .bashrc):
Joerg Hoehle proposed patching the winewrapper to adjust DYLD_FALLBACK_LIBRARY_PATH every time wine is invoked. For some reason, the patch was rejected (perhaps changing PATH variables or symlinking should be done upstream by XQuartz?)
Translations of this page:简体中文
Mac Pro Desktop 2018
Supported Wine
| CrossOver is a polished version of Wine provided by CodeWeavers. CrossOver makes it easier to use Wine and CodeWeavers provides excellent technical support to its users. All purchases of CrossOver are used to directly fund the developers working on Wine. So CrossOver is both a great way to get support in using Wine and to support the Wine Project.
CodeWeavers provides fully functional trial versions of CrossOver. This endorsement is the primary recognition that CodeWeavers has requested in exchange for hosting the Wine web site. |
Wine Binary Packages
| WineHQ Binary Packages | ||
| These packages are built and supported by WineHQ. Please report any problems with them in WineHQ's bugzilla. |
| Android - WineHQ binary packages for Android | Maintainer:Alexandre Julliard |
| Ubuntu - WineHQ binary packages for Ubuntu 16.04, 18.04, and 19.10 Debian - WineHQ binary packages for Debian Stretch, Buster, and Bullseye |
Maintainers:Rosanne DiMesio,
|
| macOS - WineHQ binary packages for macOS 10.8 through 10.14 | Maintainer:Michael Müller |
| Distro Binary Packages | ||
| These packages are built and supported by the distros. Please report any problems with them to the package maintainer. |
| SUSE - release binary and source .rpms and daily snapshot RPMs for all openSUSE versions (11.4 up to Leap 42.3 and Tumbleweed) and SUSE Linux Enterprise 11 and 12 | Maintainer:Marcus Meissner |
| Slackware - binary txz (Slackware 14.2), and tgz (for older versions) | Maintainer:Simone Giustetti |
| FreeBSD - source for FreeBSD 5.3 or later | Maintainer:Gerald Pfeifer |
3rd Party Tools
Sometimes a customization of Wine can cause an application to work, but this change cannot be incorporated into Wine for some reason. To help overcome current deficiencies in Wine, various third party applications for end users have been made over the years. These applications are entirely unsupported by the Wine developers, however you may find them useful. For more information, see our wiki page on Third Party Applications.
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 Mac Download 2018 Free