Jason Tucker's Blog

not at all creative...

mono goes hand and hand with ms. both don't like apple

whew it's been a long time since I've posted here. I know you've all missed me. anyway, i've made the switch to Apple at home and have working on setting up my new pbook with similiar apps that are on my wintel laptop. so far it's been very very easy. until i tried to setup mono.

there really isn't a good amount of info on the web on how to setup mono on mac and what info there is, it's all out dated. so i hunkered down on friday and started a journey that i don't think will ever be completed.

first there was the install using some of the helper apps that download build and install the software for you (fink, darwinports). after spending a few hours crunching threw those, I found out that in mono 1.0 there is a bug in XSP (the cassini web server for mono) that prevents it from being run on the mac. simple fix is to update from CVS. whelp.. that didn't go as smoothly as i would have liked, after about 5 hours of fuxing with it i gave up and it never ran. reformat, rinse and then repeat. now i'm trying to build EVERYTHING from CVS and well i've clocked about 10+ hours just building all the gnome stuff.

most of my time has been spent downloading, compiling and recompiling gnome libs. mono didn't really require all that much in the ways of prereqs it's the surrounding items like monodoc, monodevelop, gtk-sharp, gtkhtml-sharp that are killing.

So today I purchased Virtual PC and some more memory. My escape from wintel was short lived but i didn't think it was gonna be easy. I guess it's still a few more months with XP ;).

Posted: Sep 19 2004, 02:30 PM by jtucker | with 4 comment(s)
Filed under: ,

Comments

Ryan Gregg said:

I've been dealing with this hassle for months now, and things are getting better, but still not great.

So far I haven't seen anything from Mono running on OS X that resembles a 1.0 release, which is unfortunate.

I've been trying to get various parts of GTK# or other GUI development working on my G4 systems, and of course haven't gotten anywhere. I've seen screenshots though, so someone must have gotten something working.

I really wish the Mono project (or Microsoft) would pay more attention to the Mac. I could really use something easier to program rapidly in than Objective-C or Java and XCode.

I may have to go the route you're going, although running Windows XP in VPC is slow and not the most smooth way of creating .NET applications that run on a Mac.
# September 19, 2004 10:39 AM

It's not all bad said:

I've had exactly the opposite experience and frankly it blew my mind... took an existing c# console app (compiled in VS) and just copied the exe and dlls over, ran the framework install from the go-mono site and then used "mono myapp.exe" from the console... everything just worked, no recompiling.

Granted, I happened to not step in the mess with the web server bug, and didn't have to worry about cocoa or gtk# bindings, and haven't done any development from inside osx, but still, was a pretty crazy experience.
# September 19, 2004 1:45 PM

Erik Dasque said:

We're making a lot of effort to make Mono on Mac a great development platform. In addition to the 1.02 release (available for download on Mac) the Cocoa# project allows you to build applications using Mono in conjunction with Apple's toolkit. I use Mono on a Mac every day and am really about it. The XSP bug you're refering to is now fixed and XCode integration is coming with XCode 2.0.
# October 4, 2004 11:01 AM

Jason Tucker said:

I've got the XSP bug fixed sort of. I now get a MALLOC error when the page is posted back to the server. I'm currently working on the 1.1.1 version of Mono and am probably gonna switch to the 1.0.2 version. Cocoa# never has compiled for me and still doesn't.
# October 4, 2004 11:16 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)