[Monodevelop-devel] Building MonoDevelop on OS X for use on other Macs

David Mitchell dmitchell at logos.com
Tue Feb 22 17:24:26 EST 2011

I dug into this further, and the issue seems to be how the zip file is
created (I neglected to mention that we've been distributing MonoDevelop
in zip form; my apologies). Here is the relevant snippet from the Mac

MonoDevelop.app.zip: MonoDevelop.app
 zip -r9uq MonoDevelop.app.zip MonoDevelop.app

We zip the file, but we don't pass the -y argument, which would cause
symlinks to be preserved. Since the app bundle symlinks to Mono, this
means that whatever I have in Versions/Current/bin/mono is copied into the
zip file, and if the target machine doesn't have this same version of Mono
installed, then MonoDevelop fails to run. I believe the Makefile should

MonoDevelop.app.zip: MonoDevelop.app
 zip -r9uyq MonoDevelop.app.zip MonoDevelop.app

I'll be pushing this change to the master and 2.4 branches of our fork and
submitting a pull request shortly.

‹ Dave

On 2/20/11 10:36 AM, "Michael Hutchinson" <m.j.hutchinson at gmail.com> wrote:

>2011/2/18 David Mitchell <dmitchell at logos.com>:
>> I followed the instructions
>> on 
>>X to
>> make a custom build of MonoDevelop.app. While it works fine on my
>> (running Mono 2.8.2), developers with versions other than 2.8.2 are
>> to run the app (or mdtool), and receive errors to the effect of
>>      [exec] The assembly mscorlib.dll was not found or could not be
>>      [exec] It should have been installed in the
>> directory.
>> Is there a way to build MonoDevelop for OS X such that it will be more
>> tolerant of other versions of Mono?
>All the builds we provide on MonoDevelop.com are built this way and
>work fine. It sounds like there's a broken Mono installation on the
>target machine. Is there any more error information?
>Michael Hutchinson

More information about the Monodevelop-devel-list mailing list