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.
+
If you obtained this as a snapshot, you will need an existing
Mono installation. To upgrade your installation, unpack both
mono and mcs:
tar xzf mcs-XXXX.tar.gz
tar xzf mono-XXXX.tar.gz
- cd mono-XXXX
+ mv mono-XXX mono
+ mv mcs-XXX mcs
+ cd mono
./autogen.sh --prefix=/usr/local
- make fullbuild
+ make
+
+ c. Building the software from SVN
+ ---------------------------------
- c. Upgrade from CVS
- -------------------
+ If you are building the software from SVN, make sure that you
+ have up-to-date mcs and mono sources:
- If you are upgrading from CVS you will need an existing Mono installation.
- First verify that you have a working installation:
+ svn co svn+ssh://USER@mono-cvs.ximian.com/source/trunk/mono
+ svn co svn+ssh://USER@mono-cvs.ximian.com/source/trunk/mcs
- echo 'class X { static void Main () { System.Console.Write("OK");}}' > x.cs
+ Then, go into the mono directory, and configure:
- Compile:
+ cd mono
+ ./autogen.sh --prefix=/usr/local
+ make
- mcs x.cs
+ This will automatically go into the mcs/ tree and build the
+ binaries there.
- And run:
+ 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
- mono x.exe
+ make EXTERNAL_MCS=/foo/bar/mcs EXTERNAL_RUNTIME=/somewhere/else/mono
+
+ If you don't have a working Mono installation
+ ---------------------------------------------
- If you get the output `OK' and no errors, you are ready to start your CVS upgrade.
+ 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 try from the beginning.
- First, make sure that you have up-to-date mcs and mono sources:
+ You can also try a slightly more risky approach that should work
+ almost all the time.
- cvs co mono mcs
+ 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:
- Then, go into the mono directory, and configure:
+ make get-monolite-latest
- cd mono
- ./autogen --prefix=/usr/local
+ This will download and automatically gunzip and untar the
+ tarball, and place the files appropriately so that you can then
+ just run:
- Then compile using the special target `fullbuild':
+ make
- make fullbuild
+ To ensure that you're using the 'monolite' distribution, you can
+ also try passing EXTERNAL_MCS=false on the make command-line.
- This step will compile and install at the same time.
+ Testing and Installation
+ ------------------------
- Failure to follow these steps will result in a broken 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
+
+ make -k check
+
+ 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/
- 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.
projects / mono.git / blobdiff