Jump to: navigation, search Translations of this page (incomplete): not yet ported. Translators, please see Discussion page. Official WineHQ packages of the development and staging branches are available for macOS 10.8 and higher. Gatekeeper must not be set to block unsigned packages. 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). See Building Wine on macOS Remove the source tree and binaries. Using MacPorts, uninstall the wine package you previously installed: Replace wine with wine-devel if you installed the development version. 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: 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 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.Wine is an open source program for running Windows software on non-Windows operating systems. While it’s most often used on Linux, Wine can run Windows software directly on a Mac, too–without requiring a Windows license or needing Windows running in the background. This isn’t necessarily the best option if you want to run Windows software on a Mac. Wine isn’t perfect, and not every application will run ideally. Some applications will crash or not run at all. Virtual machines and Boot Camp are more rock-solid options, but they do add more overhead and require a Windows installation. For apps that do work, however, Wine can be extremely useful. There are several ways to get Wine on a Mac. The official project website at WineHQ now provides official builds of Wine for Mac OS X. However, those aren’t necessarily the best option.

These Wine binaries allow you to run Windows software, but don’t provide any helpful graphical tools for installing and setting up common applications, so they’re best for advanced users already familiar with Wine. Instead, you should probably consider one of the third-party projects that take the Wine source code and build a more convenient interface on top of it, one that helps you quickly install and configure common applications. best online wine shops in europeThey often perform tweaks that you’d have to perform by hand if you were using the barebones Wine software. best wine list formatThey include their own Wine software, too, so you only have to download one thing.new wine 2015 speakers Third-party tools include WineBottler, PlayOnMac, and Wineskin.

There’s also the commercial CrossOver Mac, which is the only application here you have to pay for. We’ll be using WineBottler for this tutorial, as it seems like the most popular option among Mac users. It can create Mac .app bundles for Windows programs. The other third-party applications will work similarly. To get started, download WineBottler. Be sure to download a version that works on your release of Mac OS X. When this article was written, that meant OS X El Capitan and Yosemite users needed to download version 1.8. Open the downloaded DMG file. Drag and drop both Wine and WineBottler applications to your Applications folder to install them, just like you would any other Mac application. You can then launch WineBottler from your Applications folder. WineBottler lists a number of different programs you can easily install. For example, you could install various versions of Internet Explorer if you needed to test websites with them on your Mac. The Windows version of Steam is available, and which could allow you to run some Windows-only games on your Mac.

Choose any of these options and WineBottler will automatically download, install, and configure these applications for you. The installed application will appear under “On My Mac” in the WineBottler window. You can uninstall them from here, if you like. Click an application and it will launch in a window, receiving its own icon on your dock. To run another application that doesn’t appear in the WineBottler list, you can simply download it, then right-click or Ctrl-click its .exe file to select Open With > Wine. WineBottler allows you to quickly execute the .exe directly, if you like. You can also choose to install the application in a Mac .app file created by WineBottler. If you choose to convert it to an OS X application bundle, you will be taken to the Advanced screen in WineBottler. Provide the .exe file used to install the application and you can install it as an .app using the options here. Depending on  the application, you may need various third-party libraries from the Winetricks list, DLL override options, or runtime arguments here to make it work.