Difference between revisions of "Building mono from source"

From LSDevLinux
Jump to: navigation, search
(Initial creation)
 
m (Use <code> instead of <tt>)
Line 1: Line 1:
Unpack [http://linux.lsdev.sil.org/downloads/mono/from-source/checkout-and-build.tgz this tarball] in a directory somewhere and run <code>./checkout-and-build.sh</code>. This will also install mono into <tt>/usr/local</tt>.
+
Unpack [http://linux.lsdev.sil.org/downloads/mono/from-source/checkout-and-build.tgz this tarball] in a directory somewhere and run <code>./checkout-and-build.sh</code>. This will also install mono into <code>/usr/local</code>.
  
To ensure the use of this version of mono when you run applications, either put /usr/local/bin into your PATH or (better) use <tt>/usr/local/bin/mono ''application.exe''</tt> whenever you run an application.
+
To ensure the use of this version of mono when you run applications, either put <code>/usr/local/bin</code> into your PATH or (better) use <code>/usr/local/bin/mono ''application.exe''</code> whenever you run an application.
  
 
Running this script twice will not re-download all the mono source code, but it will reinstall mono.
 
Running this script twice will not re-download all the mono source code, but it will reinstall mono.
  
'''Note:''' the script uses the “sparse checkout” feature of Subversion to create a single top-level directory that can be updated with a single <tt>svn up</tt>, eg when updating to a new revision. You can add further directories using <tt>svn up ''directory''</tt>, eg <tt>svn up monodevelop</tt>. However, you will need to specify the revision number explicitly with -r''number''if you want this directory to be compatible with the existing directories. You can find out the revision number of your existing directories using <tt>svn info</tt>.
+
'''Note:''' the script uses the “sparse checkout” feature of Subversion to create a single top-level directory that can be updated with a single <code>svn up</code>, eg when updating to a new revision. You can add further directories using <code>svn up ''directory''</code>, eg <code>svn up monodevelop</code>. However, you will need to specify the revision number explicitly with <code>-r''number''</code> if you want this directory to be compatible with the existing directories. You can find out the revision number of your existing directories using <code>svn info</code>.

Revision as of 16:12, 14 May 2009

Unpack this tarball in a directory somewhere and run ./checkout-and-build.sh. This will also install mono into /usr/local.

To ensure the use of this version of mono when you run applications, either put /usr/local/bin into your PATH or (better) use /usr/local/bin/mono application.exe whenever you run an application.

Running this script twice will not re-download all the mono source code, but it will reinstall mono.

Note: the script uses the “sparse checkout” feature of Subversion to create a single top-level directory that can be updated with a single svn up, eg when updating to a new revision. You can add further directories using svn up directory, eg svn up monodevelop. However, you will need to specify the revision number explicitly with -rnumber if you want this directory to be compatible with the existing directories. You can find out the revision number of your existing directories using svn info.