8 1. Compilation and Installation
9 ===============================
14 To build Mono, you will need the following components:
18 Available from: http://www.freedesktop.org/Software/pkgconfig
22 Available from: http://www.gtk.org/
24 Optional dependencies:
28 If you want to get support for System.Drawing, you will need to get
31 b. Building the Software
32 ------------------------
34 If you obtained this package as an officially released tarball,
35 this is very simple, use configure and make:
37 ./configure --prefix=/usr/local
41 Mono supports a JIT engine on x86, SPARC, S/390, AMD64 and PowerPC systems.
43 If you obtained this as a snapshot, you will need an existing
44 Mono installation. To upgrade your installation, unpack both
47 tar xzf mcs-XXXX.tar.gz
48 tar xzf mono-XXXX.tar.gz
52 ./autogen.sh --prefix=/usr/local
55 c. Building the software from SVN
56 ---------------------------------
58 If you are building the software from SVN, make sure that you
59 have up-to-date mcs and mono sources:
61 svn co svn+ssh://USER@mono-cvs.ximian.com/source/trunk/mono
62 svn co svn+ssh://USER@mono-cvs.ximian.com/source/trunk/mcs
64 Then, go into the mono directory, and configure:
67 ./autogen.sh --prefix=/usr/local
70 This will automatically go into the mcs/ tree and build the
73 This assumes that you have a working mono installation, and that
74 there's a C# compiler named 'mcs', and a corresponding IL
75 runtime called 'mono'. You can use two make variables
76 EXTERNAL_MCS and EXTERNAL_RUNTIME to override these. e.g., you
79 make EXTERNAL_MCS=/foo/bar/mcs EXTERNAL_RUNTIME=/somewhere/else/mono
81 If you don't have a working Mono installation
82 ---------------------------------------------
84 If you don't have a working Mono installation, an obvious choice
85 is to install the latest released packages of 'mono' for your
86 distribution and try from the beginning.
88 You can also try a slightly more risky approach that should work
91 This works by first getting the latest version of the 'monolite'
92 distribution, which contains just enough to run the 'mcs'
93 compiler. You do this with:
95 make get-monolite-latest
97 This will download and automatically gunzip and untar the
98 tarball, and place the files appropriately so that you can then
103 To ensure that you're using the 'monolite' distribution, you can
104 also try passing EXTERNAL_MCS=false on the make command-line.
106 Testing and Installation
107 ------------------------
109 You can run (part of) the mono and mcs testsuites with the command:
113 All tests should pass.
115 If you want more extensive tests, including those that test the
116 class libraries, you need to re-run 'configure' with the
117 '--enable-nunit-tests' flag, and try
121 Expect to find a few testsuite failures. As a sanity check, you
122 can compare the failures you got with
124 http://go-mono.com/tests/displayTestResults.php
126 You can now install mono with:
130 Failure to follow these steps may result in a broken installation.
135 Once you have installed the software, you can run a few programs:
151 See the man pages for mono(1), mint(1), monodis(1) and mcs(2)
158 Contains the web site contents.
161 Technical documents about the Mono runtime.
164 Configuration files installed as part of the Mono runtime.
167 The core of the Mono Runtime.
170 The object system and metadata reader.
173 The Just in Time Compiler.
176 CIL executable Disassembler
179 Common code for the JIT and the interpreter.
182 The I/O layer and system abstraction for
183 emulating the .NET IO model.
186 Common Intermediate Representation, XML
187 definition of the CIL bytecodes.
190 Interpreter for CLI executables.
193 Architecture specific portions.
197 Manual pages for the various Mono commands and programs.
201 Scripts used to invoke Mono and the corresponding program.
205 A directory that contains the Makefiles that link the
206 mono/ and mcs/ build systems.