Building MonoDevelop on OS X

Building

Before running the configure script, point aclocal at a directory containing the pkgconfig M4 macro (pkg.m4), e.g.

export ACLOCAL_FLAGS="-I /Library/Frameworks/Mono.framework/Versions/Current/share/aclocal"

and ensure that the Mono framework comes first in your PATH so you do not end up accidentally using conflicting versions of utilities from packages such as MacPorts:

export PATH="/Library/Frameworks/Mono.framework/Versions/Current/bin:$PATH"

NOTE: Please ensure that you have the very latest Mono MDK.

Check out MD, configure using the Mac profile:

git clone git://github.com/mono/monodevelop.git
pushd monodevelop
./configure --profile=mac
make
make run

NOTE: DO& NOT use configure --select on Mac - the Mac profile passes adds required arguments to the configuration of main.  Instead edit profiles/mac manually to add any additional modules.

IMPORTANT: Do not install MonoDevelop into the install prefix. MonoDevelop will pick up libraries from the prefix automatically. If you configured with a non-default prefix, then when you build an app bundle, the entire prefix will be merged into the app bundle.

Building extras

To include additional addins from extras in the build, instead of using the Mac profile, use configure --select to select addins. This will write the default profile. Next, replace the line in profiles/default that begins with "main"  with the one from profiles/mac, then run configure again using the default profile.

Running

In order to use make run to run MD, add the GTK+ libraries' path to the Mac dynamic loader path:

export DYLD_FALLBACK_LIBRARY_PATH=/Library/Frameworks/Mono.framework/Versions/Current/lib:/lib:/usr/lib

Building the App package

To build the app package, navigate to the OS X build directory:

cd main/build/MacOSX

From here, build the MonoDevelop.app or a zipped version using make MonoDevelop.app or make MonoDevelop.app.zip respectively. You can then build the .dmg using the ./make-dmg-bundle.sh script. To include addins from extras, manually copy their build directories into the MonoDevelop.app directory, e.g.

cp -r ../../../extras/MonoDevelop.AspNet.Mvc/build/* MonoDevelop.app/Contents/MacOS/lib/monodevelop/AddIns/MonoDevelop.AspNet.Mvc/

Main

Building main is straightforward. Open main/Main.sln, select the mac configuration, and run the Build command. Note that running MonoDevelop from within MD will currently only work if you export DYLD_FALLBACK_LIBRARY_PATH as described above.


Extras

Loading the full MonoDevelop.mdw workspace and building the addin solutions from extras will only work if the Makefiles' configure script has been run. Even then, not all of them will build correctly. Until this is resolved, use the makefiles to build extras.