This is Mono.
-1. Installation
-2. Using Mono
-3. Directory Roadmap
+ 1. Installation
+ 2. Using Mono
+ 3. Directory Roadmap
1. Compilation and Installation
===============================
Available from: http://www.freedesktop.org/Software/pkgconfig
- * glib 2.0
+ * glib 2.4
Available from: http://www.gtk.org/
- Optional dependencies:
+ On Itanium, you must obtain libunwind:
- * ICU library
+ http://www.hpl.hp.com/research/linux/libunwind/download.php4
- http://oss.software.ibm.com/icu/index.html
+ On Solaris, make sure that you used GNU tar to unpack this package, as
+ Solaris tar will not unpack this correctly, and you will get strange errors.
- You will need this one to get complete support for the international
- features of the .NET Framework.
+ On Solaris, make sure that you use the GNU toolchain to build the software.
- * Cairo and libgdiplus
+ Optional dependencies:
+
+ * libgdiplus
If you want to get support for System.Drawing, you will need to get
- both Libgdiplus and Cairo.
+ Libgdiplus.
b. Building the Software
------------------------
make
make install
- Mono supports a JIT engine on x86, SPARC and PowerPC systems.
- The various commands that ship with Mono default to the JIT engine
- on x86 and SPARC, to turn it on for PPC systems, use the --with-jit=yes
- command line option to configure.
-
- MacOS X Users: you will need to download the latest Boehm GC
- Alpha release for garbage collection to work properly.
+ Mono supports a JIT engine on x86, SPARC, SPARCv9, S/390, AMD64, ARM
+ and PowerPC systems.
If you obtained this as a snapshot, you will need an existing
Mono installation. To upgrade your installation, unpack both
mv mcs-XXX mcs
cd mono
./autogen.sh --prefix=/usr/local
- make bootstrap
+ make
- c. Upgrade from CVS
- -------------------
+ c. Building the software from SVN
+ ---------------------------------
- If you are upgrading from CVS you will need an existing Mono installation.
- First verify that you have a working installation:
+ If you are building the software from SVN, make sure that you
+ have up-to-date mcs and mono sources:
- echo 'class X { static void Main () { System.Console.Write("OK");}}' > x.cs
+ svn co svn+ssh://USER@mono-cvs.ximian.com/source/trunk/mono
+ svn co svn+ssh://USER@mono-cvs.ximian.com/source/trunk/mcs
- Compile:
+ Then, go into the mono directory, and configure:
- mcs x.cs
+ cd mono
+ ./autogen.sh --prefix=/usr/local
+ make
- And run:
+ This will automatically go into the mcs/ tree and build the
+ binaries there.
- mono x.exe
+ This assumes that you have a working mono installation, and that
+ there's a C# compiler named 'mcs', and a corresponding IL
+ runtime called 'mono'. You can use two make variables
+ EXTERNAL_MCS and EXTERNAL_RUNTIME to override these. e.g., you
+ can say
- If you get the output `OK' and no errors, you are ready to start your CVS upgrade.
+ make EXTERNAL_MCS=/foo/bar/mcs EXTERNAL_RUNTIME=/somewhere/else/mono
+
+ If you don't have a working Mono installation
+ ---------------------------------------------
- First, make sure that you have up-to-date mcs and mono sources:
+ If you don't have a working Mono installation, an obvious choice
+ is to install the latest released packages of 'mono' for your
+ distribution and running autogen.sh; make; make install in the
+ mono module directory.
- cvs co mono mcs
+ You can also try a slightly more risky approach: this may not work,
+ so start from the released tarball as detailed above.
- Then, go into the mono directory, and configure:
+ This works by first getting the latest version of the 'monolite'
+ distribution, which contains just enough to run the 'mcs'
+ compiler. You do this with:
- cd mono
- ./autogen.sh --prefix=/usr/local
+ make get-monolite-latest
- Then compile using the special target `fullbuild':
+ This will download and automatically gunzip and untar the
+ tarball, and place the files appropriately so that you can then
+ just run:
- make fullbuild
+ make
+
+ To ensure that you're using the 'monolite' distribution, you can
+ also try passing EXTERNAL_MCS=false on the make command-line.
+
+ Testing and Installation
+ ------------------------
+
+ You can run (part of) the mono and mcs testsuites with the command:
+
+ make check
+
+ All tests should pass.
+
+ If you want more extensive tests, including those that test the
+ class libraries, you need to re-run 'configure' with the
+ '--enable-nunit-tests' flag, and try
- This step will compile and install at the same time.
+ make -k check
- Failure to follow these steps will result in a broken installation.
+ Expect to find a few testsuite failures. As a sanity check, you
+ can compare the failures you got with
+ http://go-mono.com/tests/displayTestResults.php
+
+ You can now install mono with:
+
+ make install
+
+ Failure to follow these steps may result in a broken installation.
2. Using Mono
=============
* runtime engine
mono program.exe
- or
- mint program.exe
* C# compiler
3. Directory Roadmap
====================
- doc/
- Contains the web site contents.
-
docs/
Technical documents about the Mono runtime.
metadata/
The object system and metadata reader.
- jit/
+ mini/
The Just in Time Compiler.
dis/
definition of the CIL bytecodes.
interp/
- Interpreter for CLI executables.
+ Interpreter for CLI executables (obsolete).
arch/
Architecture specific portions.
runtime/
- A directory holding a pre-compiled version of the Mono
- runtime.
-
+ A directory that contains the Makefiles that link the
+ mono/ and mcs/ build systems.