Mono open source ECMA CLI, C# and .NET implementation.
C# C C++ JavaScript PLpgSQL ASP Other
Pull request Compare This branch is 2732 commits ahead, 30567 commits behind mono:master.
Latest commit 715f2d6 Mar 20, 2017 @erique erique committed on GitHub add support for virtual path remapping (#486)
add support for virtual path remapping through mono_unity_register_path_remapper() & MonoIO.RemapPath()

* compile warning and error fixes to virtual path remapping

* fix leak with virtual path remapping
Failed to load latest commit information.
add_to_build_results/monodistribution Report error codes from batch files. Apr 20, 2015
data Enable IPv6 support in the config files Jan 8, 2016
docs add mono_class_is_blittable Jan 9, 2017
eglib Updates for Tizen SDK 2.3.0 Oct 29, 2014
external/buildscripts Merge pull request #458 from Unity-Technologies/tizen-staging Jan 24, 2017
ikvm-native 2009-05-24 Zoltan Varga <> May 24, 2009
libgc Fix GC_approx_sp on gcc 5 Apr 19, 2016
man 2010-02-10 Geoff Norton <> Feb 11, 2010
mcs add support for virtual path remapping (#486) Mar 20, 2017
mono add support for virtual path remapping (#486) Mar 20, 2017
msvc add support for virtual path remapping (#486) Mar 20, 2017
notes Doc Doc Jul 2, 2001
perl_lib add unity build scripts & perl helper modules Oct 26, 2010
po Add .gitignore. Feb 28, 2009
runtime Fix build with new automake. Oct 22, 2013
samples 2009-06-14 Zoltan Varga <> Jun 14, 2009
scripts Report error codes from batch files. Apr 20, 2015
support [System] Fix DeflateStream throw on empty flush, double flush. Fixes … Mar 10, 2017
tools Backport of r156903 May 7, 2010
tuning [audit] Update safecall list for System.Timezone Jun 15, 2016
unity Merge pull request #464 from Unity-Technologies/unity-staging-memory-… Feb 21, 2017
web Create .gitignore's. Feb 28, 2009
.cproject Add eclipse project files. Jul 30, 2012
.gitignore better .gitignore patterns for temp build folders Jul 21, 2014
.project Add eclipse project files. Jul 30, 2012
AUTHORS Add Dietmar to Authors Feb 12, 2002
CMakeLists.txt 2009-06-15 Zoltan Varga <> Jun 15, 2009
COPYING.LIB Ugh, I had the GPL here, its the LGPL Feb 19, 2002
ChangeLog 2010-04-26 Zoltan Varga <> Apr 26, 2010
LICENSE Clarified details regarding non-LGPL use to specify both Mono and Moo… Jan 29, 2009 Forgot this May 24, 2009
NEWS Update Oct 7, 2005
README kick buildbot Jul 2, 2009
README.vsnet 2006-08-31 Zoltan Varga <> Aug 31, 2006
acinclude.m4 2009-11-12 Zoltan Varga <> Nov 12, 2009 * (EXTRA_DIST): Update. Sep 16, 2008
config.xarm-windows.h Windows/ARM crosscompiler: Jun 13, 2012 Use icall to invoke Android getifaddrs methods. Jan 6, 2017
mkinstalldirs Add mkinstalldirs Sep 15, 2008 fix glib dependency on SLE problem Apr 12, 2010 Thu Feb 1 12:29:23 CET 2007 Paolo Molaro <> Feb 1, 2007
mono-win32-setup-light.bmp add windows distribition scripts Aug 18, 2003
monowiz.win32.nsi * monowiz.win32.nsi: normalized line-endings to unix (LF) May 27, 2004
nls.m4 * (EXTRA_DIST): Update. Sep 16, 2008
po.m4 Add in non-symlink form Sep 15, 2008
progtest.m4 * (EXTRA_DIST): Update. Sep 16, 2008
winconfig.h Windows/ARM crosscompiler: Jun 13, 2012


This is Mono.

	1. Installation
	2. Using Mono
	3. Directory Roadmap

1. Compilation and Installation

   a. Build Requirements

	To build Mono, you will need the following components:

		* pkg-config

		  Available from:

		* glib 2.4

		  Available from:

	On Itanium, you must obtain libunwind:

	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.

	On Solaris, make sure that you use the GNU toolchain to build the software.

	Optional dependencies:

		* libgdiplus

		  If you want to get support for System.Drawing, you will need to get

		* libzlib

		  This library and the development headers are required for compression
		  file support in the 2.0 profile.

    b. Building the Software
	If you obtained this package as an officially released tarball,
	this is very simple, use configure and make:

		./configure --prefix=/usr/local
		make install

	Mono supports a JIT engine on x86, SPARC, SPARCv9, S/390,
	S/390x, 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
	mono and mcs:

		tar xzf mcs-XXXX.tar.gz
		tar xzf mono-XXXX.tar.gz
		mv mono-XXX mono
		mv mcs-XXX mcs
		cd mono
		./ --prefix=/usr/local

	The Mono build system is silent for most compilation commands.
	To enable a more verbose compile (for example, to pinpoint
	problems in your makefiles or your system) pass the V=1 flag to make, like this:

		 make V=1

    c. Building the software from SVN

	If you are building the software from SVN, make sure that you
	have up-to-date mcs and mono sources:

		svn co svn+ssh://
		svn co svn+ssh://

	Then, go into the mono directory, and configure:

		cd mono
		./ --prefix=/usr/local

	For people with non-standard installations of the auto* utils and of
	pkg-config (common on misconfigured OSX and windows boxes), you could get
	an error like this:

	./configure: line 19176: syntax error near unexpected token `PKG_CHECK_MODULES(BASE_DEPENDENCIES,' ...

	This means that you need to set the ACLOCAL_FLAGS environment var
	when invoking, like this:

		ACLOCAL_FLAGS="-I $acprefix/share/aclocal" ./ --prefix=/usr/loca
	where $acprefix is the prefix where aclocal has been installed.

	This will automatically go into the mcs/ tree and build the
	binaries there.

	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

	  make EXTERNAL_MCS=/foo/bar/mcs EXTERNAL_RUNTIME=/somewhere/else/mono
	If you don't have a working Mono installation

	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; make; make install in the
	mono module directory.

	You can also try a slightly more risky approach: this may not work,
	so start from the released tarball as detailed above.

	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:

		make get-monolite-latest

	This will download and automatically gunzip and untar the
	tarball, and place the files appropriately so that you can then
	just run:


	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

		make -k check

	Expect to find a few testsuite failures.  As a sanity check, you
	can compare the failures you got with

	You can now install mono with:

		make install

	Failure to follow these steps may result in a broken installation. 

    d. Common Configuration Options

	The following are the configuration options that someone
	building Mono might want to use:

	--with-gc=[boehm, included, sgen, none]

		Selects the garbage collector engine to use, the
	  	default is the "included" value.
			This is the default value, and its
	  		the most feature complete, it will allow Mono
		  	to use typed allocations and support the

			It is essentially a slightly modified Boehm GC

			This is used to use a system-install Boehm GC,
			it is useful to test new features available in
			Boehm GC, but we do not recommend that people
			use this, as it disables a few features.

			The under-development Generational GC for
		  	Mono, do not use this in production.

			Disables the inclusion of a garbage


		Controls how Mono should access thread local storage,
	  	pthread forces Mono to use the pthread APIs, while
	  	__thread uses compiler-optimized access to it.

	  	Although __thread is faster, it requires support from
	  	the compiler, kernel and libc.   Old Linux systems do
	  	not support with __thread.

		This value is typically pre-configured and there is no
	  	need to set it, unless you are trying to debug a


		Experimental: Use at your own risk, it is known to
		cause problems with garbage collection and is hard to
	 	reproduce those bugs.

		This controls whether Mono will install a special
	  	signal handler to handle stack overflows.   If set to
	  	"yes", it will turn stack overflows into the
	  	StackOverflowException.  Otherwise when a stack
	  	overflow happens, your program will receive a
	  	segmentation fault.

		The configure script will try to detect if your
	  	operating system supports this.   Some older Linux
	  	systems do not support this feature, or you might want
	  	to override the auto-detection.


		This controls whether `mono' should link against a
	  	static library (libmono.a) or a shared library

		This defaults to yes, and will improve the performance
	  	of the `mono' program. 

		This only affects the `mono' binary, the shared
	  	library will always be produced for
	  	developers that want to embed the runtime in their


		The default value for this is `yes', and it makes Mono
	  	generate code which might be slightly slower on
	  	average systems, but the resulting executable will run
	  	faster under the Xen virtualization system.


		Enable support for GC heaps larger than 3GB.

		This value is set to `no' by default.


		Controls whether the IKVM JNI interface library is
	  	built or not.  This is used if you are planning on
	  	using the IKVM Java Virtual machine with Mono.

		This defaults to `yes'.


		Whether you want to build the 2.x libraries (support
		for Generics and the 2.0/3.5 APIS).

	  	It defaults to `yes'.


		Whether you want to generate the Silverlight/Moonlight
		libraries and toolchain in addition to the default
		(1.1 and 2.0 APIs).

		This will produce the `smcs' compiler which will reference
		the Silverlight modified assemblies (mscorlib.dll,
		System.dll, System.Code.dll and System.Xml.Core.dll) and turn
	  	on the LINQ extensions for the compiler.


		This is used to configure where should Mono look for
	  	libgdiplus when running the System.Drawing tests.

		It defaults to `installed', which means that the
	  	library is available to Mono through the regular
	  	system setup.

		`sibling' can be used to specify that a libgdiplus
	  	that resides as a sibling of this directory (mono)
	  	should be used.

		Or you can specify a path to a libgdiplus.


		Use this option to disable the use of shared memory in
		Mono (this is equivalent to setting the MONO_DISABLE_SHM
		environment variable, although this removes the feature

		Disabling the shared memory support will disable certain
		features like cross-process named mutexes.


		Use this feature to specify optional runtime
	  	components that you might not want to include.  This
	  	is only useful for developers embedding Mono that
	  	require a subset of Mono functionality.

		The list is a comma-separated list of components that
	  	should be removed, these are:

			Disables support for the Ahead of Time

			Support for the Mono.Management assembly and the
			VMAttach API (allowing code to be injected into
			a target VM)

			Disables COM support.

			Drop debugging support.

			Disables support for System.Decimal.

			By default Mono comes with a full table
			of messages for error codes.   This feature
			turns off uncommon error messages and reduces
			the runtime size.

			Generics support.  Disabling this will not
			allow Mono to run any 2.0 libraries or
			code that contains generics.

			Removes the JIT engine from the build, this reduces
			the executable size, and requires that all code
			executed by the virtual machine be compiled with
			Full AOT before execution.

			Disables support for large assemblies.

	  		Disables support for debug logging.

			Support for Platform Invocation services,
			disabling this will drop support for any
			libraries using DllImport.

			Removes support for MONO_IOMAP, the environment
			variables for simplifying porting applications that 
			are case-insensitive and that mix the Unix and Windows path separators.

			Disables support for the default profiler.

			Drop System.Reflection.Emit support

			Drop support for saving dynamically created
			assemblies (AssemblyBuilderAccess.Save) in

			Disables support for AppDomain's shadow copies
			(you can disable this if you do not plan on 
			using appdomains).

			Disables support for the Mono.SIMD intrinsics

			Disables compilation for the SSA optimization
			framework, and the various SSA-based


		This enables the use arrays whose indexes are larger
		than Int32.MaxValue.   

		By default Mono has the same limitation as .NET on
		Win32 and Win64 and limits array indexes to 32-bit
		values (even on 64-bit systems).

		In certain scenarios where large arrays are required,
		you can pass this flag and Mono will be built to
		support 64-bit arrays.

		This is not the default as it breaks the C embedding
		ABI that we have exposed through the Mono development


		Use this option to enable the garbage collector to use
		multiple CPUs to do its work.  This helps performance
		on multi-CPU machines as the work is divided across CPUS.

		This option is not currently the default as we have
		not done much testing with Mono.


		On Solaris and MacOS X builds a version of the Mono
		runtime that contains DTrace probes and can
		participate in the system profiling using DTrace.


		Mono uses /dev/random to obtain good random data for
	  	any source that requires random numbers.   If your
	  	system does not support this, you might want to
	  	disable it.

		There are a number of runtime options to control this
	  	also, see the man page.

2. Using Mono

	Once you have installed the software, you can run a few programs:

	* runtime engine

		mono program.exe

	* C# compiler

		mcs program.cs

	* CIL Disassembler

		monodis program.exe

	See the man pages for mono(1), mint(1), monodis(1) and mcs(2)
	for further details.

3. Directory Roadmap

		Technical documents about the Mono runtime.

		Configuration files installed as part of the Mono runtime.

		The core of the Mono Runtime.

			The object system and metadata reader.

			The Just in Time Compiler.

			CIL executable Disassembler

			Common code for the JIT and the interpreter.

			The I/O layer and system abstraction for 
			emulating the .NET IO model.

			Common Intermediate Representation, XML
			definition of the CIL bytecodes.

			Interpreter for CLI executables (obsolete).

			Architecture specific portions.


		Manual pages for the various Mono commands and programs.


		Some simple sample programs on uses of the Mono
		runtime as an embedded library.   


		Scripts used to invoke Mono and the corresponding program.


		A directory that contains the Makefiles that link the
		mono/ and mcs/ build systems.


		If the directory ../olive is present (as an
		independent checkout) from the Mono module, that
		directory is automatically configured to share the
		same prefix than this module gets.