[Mono-osx] Obj-C#, Cocoa# and bundles.

Andreas Färber andreas.faerber at web.de
Wed Jan 23 07:41:40 EST 2008

Am 22.01.2008 um 22:46 schrieb Sijmen Mulder:

> 2. [...] I have an application
> that basically consists of a .NET DLL assembly, and a generic launcher
> (doing the system work) for every specific platform. My idea was to
> write an Objective-C launcher/backend for the Mac (as opposed to fully
> Cocoa#), as I need to a few native libraries. The program should be
> able to access most of the .NET assembly. Note that it's Objective-C
> calling .NET here, not the other way around. No Cocoa classes need to
> be exposed to the .NET code. Are either Obj-C# or Cocoa# mature enough
> to do this? Which one would be the best option?

The most mature option is embedding Mono through its C API, like on  
every other platform.

There's also Dumbarton, which appeared to wrap the C API into an ObjC  

> 4. Anything else I should be aware of?

If you embed Mono, beware of which glib version your Mono links to; on  
Leopard to compile you may also need to apply a patch to glib headers  
concerning their definition of "inline".


More information about the Mono-osx mailing list