![]() ![]() No longer developed, no longer maintained, deprecated. Bundled with Mono.īinding to the native Cocoa APIs, but requires manual use of Objective-C selectors to work with, relatively thin wrapper around the underlying APIs. The Windows.Forms API was frozen in time by Microsoft. Bundled with Mono.Ĭross platform implementation of Microsoft’s Windows.Forms. Applications look foreign on OSX.Īctively developed, cross platform. Strongly typed C# binding to the cross platform Gtk+ API. This will be the new default binding for Mono on OSX. There are a few choices to build client applications on OSX, you should pick the technology that better fits your goals, your choices are:Īctively developed, builds on the design lessons from MonoTouch but still incomplete. Supporting 64-bit Mono across the board would also require us to ship a 64-bit Gtk+ stack and that would increase the download size for most users. MonoMac bindings have not been ported to 64 bits.MonoDevelop uses Carbon for its menu integration so it would not run on a 64-bit VM.Our Windows.Forms implementation uses Carbon, and as such, it would not work with a 64-bit Mono.The 64 bit support has a few limitations today which is why we have not entirely switched to it: In the future we will ship both mono and mono64 binaries for our users. Support for 64-bit VMs as of Mono 2.10 is only available if you build Mono from source code and install your own copy of the VM. ![]() The Mono packages published on this web site provide a 32-bit Mono VM. You will have a choice of GUI toolkits for building your application, from pure cross platform, to Mac-specific using MonoMac. Most users would be using the MonoDevelop IDE to create their projects. To build applications you can use “mcs”, to run then you can use mono.įrom a Terminal shell, you can try it out: $ vi hello.cs Using Mono on MacOS XĪt 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. ![]() Our packages currently require Mono OSX 10.7 or better, for older versions, you will need to build from source code. These will have to be compiled from source. The MacOS X Mono package does not include Gtk#, XSP or mod_mono. If you’d like to access the mono manpages you’ll have to add /Library/Frameworks/amework/Versions/Current/man to your manpath. Symlinks are created for the executables in /usr/bin. This package installs as a framework to /Library/Framework (the same way the Java packages are installed).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |