Adjacent posts
« New Software: Bzr Notification Plugin Sphinx Templates »Recently, I had to get MonoDevelop working on CentOS 5 for a project. Here is my blow-by-blow summary of how to get it working. The procedure is designed for CentOS 5, and it works on my Fedora 8 system as well. Since most of the activity is just compiling stuff from source, it should be pretty easy to follow on a different distribution. It’s just a matter of getting the correct packages installed in the preparation phase.
Note: In this document, all source code will go in /usr/src/monodevelop-install. All installed packages will go in /usr/local/software. mkdir -p /usr/local/software/mono-1.9 sudo chown -R `whoami` /usr/local/software # (Be careful if you already have software here)
mkdir -p /usr/src/monodevelop-install
yum install glib2-devel pango-devel gtk2-devel glade2-devel libgnome-devel gnome-desktop-devel gnome-panel-devel libgnomeprintui22-devel gtksourceview-devel ruby ruby-rdoc gtkhtml38-devel wget # (maybe openssl-devel also) echo 'PATH="/usr/local/software/mono-1.9/bin:$PATH"' > /usr/local/software/mono-1.9/env.sh echo 'export PKG_CONFIG_PATH=/usr/local/software/mono-1.9/lib/pkgconfig' >> /usr/local/software/mono-1.9/env.sh echo 'export LD_LIBRARY_PATH=/usr/local/software/mono-1.9/lib' >> /usr/local/software/mono-1.9/env.sh
Important: You must always run this command before using Monodevelop, and also before continuing on with this procedure.
source /usr/local/software/mono-1.9/env.shIn this document, Monodevelop is not completely integrated into the GUI, menus, etc. for a couple of reasons:
Getting Monodevelop to show up in the menus is somewhat distro-specific. For RPM-based distros, look into setting the $XDG_DATA_DIRS variable in /etc/X11/xinit/xinitrc.d/, but you will also have to get the path working. For Debian-based distros, look into doing the same thing in /etc/X11/Xsession.d. And if you happen to be trying this on Solaris, look into /usr/dt/config/Xsession.d. Oh and by the way, the .desktop file that ships with Monodevelop is invalid for my Fedora 8 system! So you will have to manually edit it and (IIRC) remove the TryExec line. As you can see, this requires a bit of mucking with “standard” package-maintained config files, which I am hesitant to do because it violates the objective of isolation.All this means you will always have to first source the small shell script which sets up the correct environment variables whenever you want to run Monodevelop.
This is optional, but many .NET applications build with it, so it might be worth throwing in there.
cd /usr/src/monodevelop-install wget http://downloads.sourceforge.net/nant/nant-0.85-bin.tar.gz tar xzf nant-0.85-bin.tar.gz -C /usr/local/software/mono-1.9 echo ’#!/bin/bash’ > /usr/local/software/mono-1.9/bin/nant echo ‘mono /usr/local/software/mono-1.9/nant-0.85/bin/NAnt.exe ”$@”’ >> /usr/local/software/mono-1.9/bin/nant chmod +x /usr/local/software/mono-1.9/bin/nantYou’re done! Run it!
monodevelopFeel free to contact me if you have any input to add. I will try to add another post for Debian/Ubuntu and possibly Solaris in the future.
Posted in Free Software Comments Off
Comments are closed.
Copyright © Proven Corporation Co., Ltd., Thailand. All rights reserved.
Free software and open source solutions and support in Thailand, Singapore, and Southeast Asia.
Feel free to contact us.