| Newsgroups |
gmane.comp.gnome.mono.patches |
| Message-ID |
<00000142068e83d7-ddcd5a05-1b5b-4652-b228-b6ed66111e02-000000@email.amazonses.com> |
Branch: refs/heads/readmeUpdate
Home: https://github.com/mono/mono
Compare: https://github.com/mono/mono/compare/1e107ece1fac...91c622af1a21
Commit: 91c622af1a21b5b13806dd4c25f334111726b87b
Author: Therzok <[email protected]> (Therzok)
Date: 2013-10-29 23:29:49 GMT
URL: https://github.com/mono/mono/commit/91c622af1a21b5b13806dd4c25f334111726b87b
Try out 2
Changed paths:
M README.md
Modified: README.md
===================================================================
@@ -17,30 +17,31 @@ a. Build Requirements
`http://www.hpl.hp.com/research/linux/libunwind/download.php4`
- * 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
- * On Solaris, make sure that you use the GNU toolchain to build the software.
+ 1. 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.
- Optional dependencies:
+ 2. Make sure that you use the GNU toolchain to build the software.
- * libgdiplus
+ 3. Optional dependencies:
+ * libgdiplus
- If you want to get support for System.Drawing, you will need to get
- Libgdiplus. This library in turn requires glib and pkg-config:
+If you want to get support for System.Drawing, you will need to get
+Libgdiplus. This library in turn requires glib and pkg-config:
- * pkg-config
+ * pkg-config
- Available from: http://www.freedesktop.org/Software/pkgconfig
+Available from: http://www.freedesktop.org/Software/pkgconfig
- * glib 2.4
+ * glib 2.4
- Available from: http://www.gtk.org/
+Available from: http://www.gtk.org/
- * libzlib
+ * libzlib
- This library and the development headers are required for compression
- file support in the 2.0 profile.
+This library and the development headers are required for compression
+file support in the 2.0 profile.
b. Building the Software
------------------------
@@ -78,15 +79,14 @@ c. Building the software from GIT
If you are building the software from GIT, make sure that you
have up-to-date mcs and mono sources:
-If you are an anonymous user:
+ * If you are an anonymous user:
`git clone git://github.com/mono/mono.git`
-If you are a Mono contributors with read/write privileges:
+* If you are a Mono contributors with read/write privileges:
`git clone [email protected]:mono/mono.git`
-
Then, go into the mono directory, and configure:
cd mono
@@ -97,9 +97,9 @@ 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,' ...`
+`./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
+This means that you need to set the ACLOCAL_FLAGS environment variable
when invoking autogen.sh, like this:
`ACLOCAL_FLAGS="-I $acprefix/share/aclocal" ./autogen.sh --prefix=/usr/local`
@@ -113,7 +113,7 @@ 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
+can say:
`make EXTERNAL_MCS=/foo/bar/mcs EXTERNAL_RUNTIME=/somewhere/else/mono`
@@ -122,7 +122,7 @@ 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 autogen.sh; make; make install in the
+distribution and running `autogen.sh; make; make install` in the
mono module directory.
You can also try a slightly more risky approach: this may not work,
@@ -130,7 +130,7 @@ 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:
+compiler. You do this with:
# Run the following line after ./autogen.sh
make get-monolite-latest
@@ -146,30 +146,23 @@ And that will use the files downloaded by 'make get-monolite-latest.
Testing and Installation
------------------------
-You can run (part of) the mono and mcs testsuites with the command:
-
-`make check`
+You can run **(part of)** the mono and mcs test suites with the command: `make check`
All tests should pass.
-If you want more extensive tests, including those that test the
+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
+'--enable-nunit-tests' flag, and try: `make -k check`
-`make -k check`
-
-Expect to find a few testsuite failures. As a sanity check, you
+Expect to find a few test suite failures. As a sanity check, you
can compare the failures you got with
`https://wrench.mono-project.com/Wrench/`
-You can now install mono with:
-
-`make install`
+You can now install mono with: `make install`
You can verify your installation by using the mono-test-install
script, it can diagnose some common problems with Mono's install.
-
Failure to follow these steps may result in a broken installation.
d. Configuration Options
@@ -509,17 +502,11 @@ Using Mono
Once you have installed the software, you can run a few programs:
- * runtime engine
-
-`mono program.exe`
-
-* C# compiler
-
-`mcs program.cs`
+* runtime engine `mono program.exe`
-* CIL Disassembler
+* C# compiler `mcs program.cs`
-`monodis program.exe`
+* CIL Disassembler `monodis program.exe`
See the man pages for mono(1), mint(1), monodis(1) and mcs(2)
for further details.
_______________________________________________
Mono-patches maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-patches