- The Wine development release 6.8 is now available. What's new in this release: Libraries installed into architecture-specific subdirectories. Secur32 library converted to PE. Support for Map object in JavaScript. Various bug fixes. The source is available now.
- The provided wine-. Ports compile on Mac OSX 10.8 and later, on MacOSX 10.8 distfiles won't download but it seems that macports will handle this directly soon. MoltenVK minimum requirement was lowered from 10.12 to 10.11.
Introduction to Mono on macOS
To install Wine on your Mac, you will need the following: macOS 10.10 (Yosemite) or above (but 10.15 Catalina is not recommended) Access to an Admin account, with password. Then, install wine and winetricks: pacman -S wine winetricks. If you don't have X11 installed (check by trying startx), install a working X11 environment from XQuartz. Use your package manager to install wine. If you don't have a package manager, consider using Homebrew: Head to brew.sh, and follow its instructions for installing. Step 1: install wine There is a really good tutorial online, written by one David Baumgold. Best tutorial I've found on installing wine on Mac - and people are still posting questions on his post more than a year after it was written. Follow the tutorial, making sure you follow steps 1-2-3.
Mono supports macOS version 10.9 (Mavericks) and later.
You can use Mono on macOS to build server, console and GUI applications. Read below for the options available for GUI application development.
Wine Mono Is Not Installed Macos
If you are interested in creating native GUI applications, use the MonoMac bindings and our MonoDevelop add-in. Read the description on MonoMac for more information on how to get started.
Installing Mono on macOS
You can use Mono either as a runtime to run existing application, or as an SDK to develop new applications with Mono.
Visit the download page to find the latest macOS package. Run it and follow the instructions there, you can either get a basic runtime, or a complete runtime plus a software development kit.
If you plan on developing applications with Mono, we suggest that you also install the MonoDevelop IDE after you install Mono.
The Mono package includes:
- The Mono Runtime
- GUI Toolkits: Windows.Forms and Gtk# for macOS.
- Note: the MonoMac GUI toolkit for native macOS GUI development is currently a separate download.
- SDK: C#, Visual Basic compilers, assemblers and tools
- XSP ASP.NET server
- Manual pages.
This package installs as a framework into /Library/Frameworks/Mono.framework (the same way the Java packages are installed). The executable binaries can be found in /Library/Frameworks/Mono.framework/Versions/Current/bin. If you’d like to access the mono manpages you’ll have to add /Library/Frameworks/Mono.framework/Versions/Current/man to your manpath. The macOS Mono package does not include Gtk#, XSP or mod_mono. These will have to be compiled from source.
Our packages currently require macOS version 10.9 or later, for older versions, you will need to build from source code.
Using Mono on macOS
At this point, you must use Mono from the command line, the usual set of commands that are available on other ports of Mono are available.
To build applications you can use “mcs”, to run then you can use mono.
From a Terminal shell, you can try it out:
Most users would be using the MonoDevelop IDE to create their projects.
You will have a choice of GUI toolkits for building your application, from pure cross platform, to Mac-specific using MonoMac.
32 and 64 bit support
The Mono packages published on this web site provide both a 32-bit and a 64-bit Mono VM.
How To Install Wine Mono
Starting from Mono 5.2 the mono command defaults to 64-bit, you can use the --arch=32/64 switch to control the bitness.
The 64 bit support has a few limitations today:
- Our Windows.Forms implementation uses Carbon, and as such, it would not work with a 64-bit Mono.
Building Client Applications
There are a few choices to build client applications on macOS, you should pick the technology that better fits your goals, your choices are:
| Toolkit | Runs on Linux | Runs on Windows | Runs on Mac | Binding Style | License | Status |
| MonoMac | no | no | yes | Strongly typed C# binding to Cocoa APIs | MIT X11 | Actively developed, builds on the design lessons from MonoTouch but still incomplete. This will be the new default binding for Mono on macOS. Separate download. |
| Gtk# | yes | yes | yes | Strongly typed C# binding to the cross platform Gtk+ API. Applications look foreign on macOS. | LGPL v2 | Actively developed, cross platform. Bundled with Mono. |
| Windows.Forms | yes | yes | yes | Cross platform implementation of Microsoft’s Windows.Forms. Applications look foreign on macOS. | MIT X11 | The Windows.Forms API was frozen in time by Microsoft. Bundled with Mono. |
| MonObjc | no | no | yes | Binding to the native Cocoa APIs, but requires manual use of Objective-C selectors to work with, relatively thin wrapper around the underlying APIs. | LGPL v3 | Actively developed. Separate download. |
| CocoaSharp | no | no | yes | Binding to the native Cocoa APIs, but requires manual use of Objective-C selectors to work with, relatively thin wrapper around the underlying APIs. | MIT X11 | No longer developed, no longer maintained, deprecated. Bundled with Mono. |
Running Mono applications on macOS
Running applications on macOS is very similar to linux systems, from the terminal:
For GTK# applications, it’s easiest to run them the same way but using xterm from X11.app
Windows.Forms
Mono’s implementation of the System.Windows.Forms API is built on top of Carbon and can only run with Mono on 32 bit systems. The look and feel of System.Windows.Forms applications mimics the Windows style and does not currently render like a native macOS application.
Third Party Libraries
ObjC# is a transparent two way bridge that allows the CLR to access the rich underlying ObjectiveC frameworks as well as providing direct access to the CLR frameworks from the ObjectiveC language.
Uninstalling Mono on macOS
Wine Mono Is Not Installed
Run this script in a terminal: