Wine (originally an acronym for "Wine Is Not an Emulator") is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems, such as Linux, macOS, & BSD. Instead of simulating internal Windows logic like a virtual machine or emulator, Wine translates Windows API calls into POSIX calls on-the-fly, eliminating the performance and memory penalties of other methods and allowing you to cleanly integrate Windows applications into your desktop. The Wine development release 2.7 is now available. What's new in this release: TCP and UDP connection support in WebServices. Various shader improvements for Direct3D 11. Improved support for high DPI settings. Partial reimplementation of the GLU library. Support for recent versions of OSMesa. Window management improvements on macOS. The source is available now. Binary packages are in the process of being built, and will appear soon at their respective download locations.

The Wine maintenance release 2.0.1 is now available. The Wine development release 2.6 is now available. Multi-threaded command stream in Direct3D. More Shader Model 5 instructions. More support for 3D textures. Better font transformations in DirectWrite. Binary packages are in the process of being built, and will appear soon at their respective download locations.Change the way you install and update apps with the all new The Developer Bundle 2017 See more special offers 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-compliant operating systems, such as Linux, OS X, and BSD. Instead of simulating internal Windows logic like a virtual machine or emulator,More...

Version 2.0: Text and Fonts More DirectWrite features are implemented, including: Drawing of underlines Renderer sees drawing effect associated with text segment Support for color fonts in COLR/CPAL format Initial font fallback support, builtin data for some of CJK ranges Support for Wine-specific font replacement registry settingsMore...best box wine 2011 OS X 10.5 or laterwine ice cream facebookWhile Wineskin has been used mainly for gaming, it is capable of running non-gaming software as well.wine of fire france ), which is a re-implementation of the Win32 API for non-Windows™ operating systems. Crossover Engine builds are built from the Wine source code used in the Crossover. Crossover is a wonderful product by CodeweaversIt does not use Apple's X11.app.  

You can have it use XQuartz.app instead of WineskinX11 if you so choose.  Wine versions from around 1.5.26+ have a Wine Mac driver that can also be used instead of needing X11. belongs to Urge Software or Wineskin, please ask permission for use. This is my Next Wine 2.0.1 / 2.7 Dev Free and open source implementation of the Windows API designed to help you seamlessly and effortlessly run Windows programs on your Mac NOTE: Unofficial Wine binaries for macOS are available on the Wine.app entry (compiled by Mike Kronenberg) and on the Darwine entry (compiled by the Darwine team). Running Windows applications on your Mac is not impossible and there are various solutions to complete the task. The first idea that comes to mind is to actually install a Windows operating on your Mac by using Boot Camp but that means that you must restart your computer to switch between the operating systems. On the other hand, you can choose to create a virtual machine via different emulators and run the apps natively but that might prove to be time consuming to set up and a bit demanding on the resources side.

Run Windows programs seamlessly on your Mac Wine, which stands for Wine Is Not an Emulator, takes a different approach: since macOS is POSIX compliant, Wine translates the Windows API calls into POSIX calls in order to be understood by Apple’s operating system. The conversion is done on-the-fly and enables you to integrate Windows applications into your workflow in no time. Support for a wide array of Windows programs Wine is a free software and volunteers work to provide out-of-the-box support for different applications. You can find which apps are Wine compatible, submit requests, view statistics and much more Wine Application Database page. The Wine developers provide the source code which you can compile yourself or you can use some of the unofficial binaries. Probably the most popular Wine binary release is Mike Kronenberg’s Wine.app which you can find Wine.app page. Additionally, you can use the Darwine team build which can be downloaded from the Darwine page.

Use Windows apps without restarting your Mac Wine is great if you need to run Windows native applications on your Mac without having to use Boot Camp and restart your system. Setting up virtual machines takes slightly more time, more resources and you might have issues if you need the Windows app to interact with your macOS. Wine simply translates the commands to a language that macOS understands: this way the resources usage is reduced and you can run apps right out of the box. Wine was reviewed by /5 Toast Titanium   Java for Mac OS X   NTFS-3G   macOS Update   OnyX DiskWarrior   VMware Fusion   Winclone   TechTool Pro   CrossOver Mac category:Home \ System UtilitiesJump to: , Contents 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, 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. 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. 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): 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 provides an --only-dependencies flag for the install command that lets you install Wine's dependencies without the wine package itself. You also probably want to pass the --devel flag to base the command on the recent development release of Wine; otherwise Homebrew will install the stable release by default: 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: 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: 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.