Run Windows-based Programs on a Mac

Download the App. Apple App Store. Got my Catalina wine mix, my floaties, and some hotties on boats (60 Photos) by: Martin. In: Bikinis, Hot Women, Hotness. Note, however, that they are not part of the Wine Project; any problems with homebrew or Macports should be reported to the respective site. From macOS Catalina Apple removed 32-bit support, which makes it impossible to use 32-bit Wine. In order to build and run Wine, you might need to install some extra software.

» News: Cryptographic Update for WineBottler 4.0.1.1

Turn Windows-based programs into Mac apps –
NOT. ;)

WineBottler packages Windows-based programs like browsers, media-players, games or business appli­ca­tions snugly into Mac app-bundles.
Your company provides you with a login, mail, calendar and contacts that only work on certain browsers?
You quickly want to test your websites in Windows-based browsers.
You want to play games, that are not ported to OS X?
Your online trading platform or accounting tool only runs on Windows?
Your audio book player is not available on OS X?
No need to install emulators, virtualizers or boot into other operating systems – WineBottler runs your Windows-based programs directly on your Mac.
This is possible thanks to a Windows-compatible subsystem, which is provided by the great OpenSource tool Wine.

WineBottler does Automated Installations:

Select from a wide range of software for which WineBottler offers automated installations. It is as easy as hitting 'Install' – and WineBottler will leave you with a neat app on your desktop. WineBottler does not come with the programs themselves, but with scripts, that take care of down­loading, configuring and installing everything into an app for you.

WineBottler can pack your .exe into an Mac .app ...

Wine Download For Mac Os Catalina Download

Double-click your .exe or .msi and convert it into an app with WineBottler. You can run the generated app like every other program on your Mac. For advanced users, WineBottler gives you a selection of options: install special dependencies and even turn your .exe into a self-contained app - that is an app, that contains everything to run it... even on other Macs. Porting to OS X never was easier ;).
Find out more - have a look at the Documentation.

... or just run that .exe.

You don't care about generating an app and just want to run it? Double-click the .exe, choose 'Run directly' and Wine will run it in a generic environment.

Enjoy, it's free!

Like Wine, WineBottler is free software. We've made it out of our own needs and now we share the result. If you are happy with it, you can keep the project rolling by sending a small Donation.

Need other Versions of WineBottler or Wine.app?

We keep selected builds for you. Versions before 1.4.1 still run on OS X Tiger and Leopard.
You find them under Downloads.

Support

If you have questions installing a certain program, please have a look at the documentation or at appdb.winehq.org first. winehq.org is the hub for all info about wine. It contains notes, hints and tricks to install all major programs.
winehq.org is NOT affiliated with WineBottler in any way. So please do NOT post bug-reports or questions about WineBottler there - write an eMail to mikesmassivemess(at)kronenberg.org and if time permits, i'll try to get your exe running.
WineBottler is my hobby and it is free, so please understand, that I can't give you a one-to-one support. If you are looking for a Wine version with great dedicated support: Note down this Promo Code: 'TANGENT' (for a 30% discount) – then head over to CrossOver.

• 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.

homebrew and MacPorts are package managers 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 or Macports should be reported to the respective site.

From macOS Catalina Apple removed 32-bit support, which makes it impossible to use 32-bit Wine.

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 provide a wine formula instead opting to use their cask system to install Winehq provided packages.

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. homebrew no longer allows force linking bison so this needs to be added to PATH manually.

Wine Download Mac Catalina

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 and XCode 9 Command Line Tools, not the versions from the App Store.
If you're running macOS Mojave, you need to do some workarounds as in 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:

Winebottler Catalina Download

Please Note: While Wine can be compiled using XCode on macOS (Compiling with XCode10 requires MacOSX10.13.sdk & setting min version to 10.7)

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.

Wine Stable Catalina Download

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?)