README 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206
  1. This is Mono.
  2. 1. Installation
  3. 2. Using Mono
  4. 3. Directory Roadmap
  5. 1. Compilation and Installation
  6. ===============================
  7. a. Build Requirements
  8. ---------------------
  9. To build Mono, you will need the following components:
  10. * pkg-config
  11. Available from: http://www.freedesktop.org/Software/pkgconfig
  12. * glib 2.4
  13. Available from: http://www.gtk.org/
  14. On Itanium, you must obtain libunwind:
  15. http://www.hpl.hp.com/research/linux/libunwind/download.php4
  16. Optional dependencies:
  17. * libgdiplus
  18. If you want to get support for System.Drawing, you will need to get
  19. Libgdiplus.
  20. b. Building the Software
  21. ------------------------
  22. If you obtained this package as an officially released tarball,
  23. this is very simple, use configure and make:
  24. ./configure --prefix=/usr/local
  25. make
  26. make install
  27. Mono supports a JIT engine on x86, SPARC, SPARCv9, S/390, AMD64 and PowerPC systems.
  28. If you obtained this as a snapshot, you will need an existing
  29. Mono installation. To upgrade your installation, unpack both
  30. mono and mcs:
  31. tar xzf mcs-XXXX.tar.gz
  32. tar xzf mono-XXXX.tar.gz
  33. mv mono-XXX mono
  34. mv mcs-XXX mcs
  35. cd mono
  36. ./autogen.sh --prefix=/usr/local
  37. make
  38. c. Building the software from SVN
  39. ---------------------------------
  40. If you are building the software from SVN, make sure that you
  41. have up-to-date mcs and mono sources:
  42. svn co svn+ssh://[email protected]/source/trunk/mono
  43. svn co svn+ssh://[email protected]/source/trunk/mcs
  44. Then, go into the mono directory, and configure:
  45. cd mono
  46. ./autogen.sh --prefix=/usr/local
  47. make
  48. This will automatically go into the mcs/ tree and build the
  49. binaries there.
  50. This assumes that you have a working mono installation, and that
  51. there's a C# compiler named 'mcs', and a corresponding IL
  52. runtime called 'mono'. You can use two make variables
  53. EXTERNAL_MCS and EXTERNAL_RUNTIME to override these. e.g., you
  54. can say
  55. make EXTERNAL_MCS=/foo/bar/mcs EXTERNAL_RUNTIME=/somewhere/else/mono
  56. If you don't have a working Mono installation
  57. ---------------------------------------------
  58. If you don't have a working Mono installation, an obvious choice
  59. is to install the latest released packages of 'mono' for your
  60. distribution and try from the beginning.
  61. You can also try a slightly more risky approach that should work
  62. almost all the time.
  63. This works by first getting the latest version of the 'monolite'
  64. distribution, which contains just enough to run the 'mcs'
  65. compiler. You do this with:
  66. make get-monolite-latest
  67. This will download and automatically gunzip and untar the
  68. tarball, and place the files appropriately so that you can then
  69. just run:
  70. make
  71. To ensure that you're using the 'monolite' distribution, you can
  72. also try passing EXTERNAL_MCS=false on the make command-line.
  73. Testing and Installation
  74. ------------------------
  75. You can run (part of) the mono and mcs testsuites with the command:
  76. make check
  77. All tests should pass.
  78. If you want more extensive tests, including those that test the
  79. class libraries, you need to re-run 'configure' with the
  80. '--enable-nunit-tests' flag, and try
  81. make -k check
  82. Expect to find a few testsuite failures. As a sanity check, you
  83. can compare the failures you got with
  84. http://go-mono.com/tests/displayTestResults.php
  85. You can now install mono with:
  86. make install
  87. Failure to follow these steps may result in a broken installation.
  88. 2. Using Mono
  89. =============
  90. Once you have installed the software, you can run a few programs:
  91. * runtime engine
  92. mono program.exe
  93. * C# compiler
  94. mcs program.cs
  95. * CIL Disassembler
  96. monodis program.exe
  97. See the man pages for mono(1), mint(1), monodis(1) and mcs(2)
  98. for further details.
  99. 3. Directory Roadmap
  100. ====================
  101. docs/
  102. Technical documents about the Mono runtime.
  103. data/
  104. Configuration files installed as part of the Mono runtime.
  105. mono/
  106. The core of the Mono Runtime.
  107. metadata/
  108. The object system and metadata reader.
  109. jit/
  110. The Just in Time Compiler.
  111. dis/
  112. CIL executable Disassembler
  113. cli/
  114. Common code for the JIT and the interpreter.
  115. io-layer/
  116. The I/O layer and system abstraction for
  117. emulating the .NET IO model.
  118. cil/
  119. Common Intermediate Representation, XML
  120. definition of the CIL bytecodes.
  121. interp/
  122. Interpreter for CLI executables.
  123. arch/
  124. Architecture specific portions.
  125. man/
  126. Manual pages for the various Mono commands and programs.
  127. scripts/
  128. Scripts used to invoke Mono and the corresponding program.
  129. runtime/
  130. A directory that contains the Makefiles that link the
  131. mono/ and mcs/ build systems.