-
Notifications
You must be signed in to change notification settings - Fork 3.8k
/
mono-beginning.xml
1294 lines (1106 loc) · 46.2 KB
/
mono-beginning.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" []>
<article>
<articleinfo>
<!-- Use "HOWTO", "mini HOWTO", "FAQ" in title, if appropriate -->
<title>Running Mono</title>
<author>
<firstname>Hinne</firstname>
<surname>Hettema</surname>
<affiliation>
<address><email>h.hettema@auckland.ac.nz</email></address>
</affiliation>
</author>
<author>
<firstname>Jaime</firstname>
<surname>Anguiano Olarra</surname>
<affiliation>
<address><email>jaime@genuara.ugr.es</email></address>
</affiliation>
</author>
<pubdate>2002-06</pubdate>
<!-- Most recent revision goes at the top; list in descending order -->
<!-- All dates specified in ISO "YYYY-MM-DD" format -->
<revhistory>
<revision>
<revnumber>0.1</revnumber>
<date>2002-06-20</date>
<authorinitials>HH</authorinitials>
<revremark>First release</revremark>
</revision>
</revhistory>
<!-- Provide a good abstract; a couple of sentences is sufficient -->
<abstract>
<para>
This document describes how to install mono on your Linux system
from the source and describes some simple experiments you can
perform with this installation.
</para>
</abstract>
</articleinfo>
<sect1 id="intro">
<title>Introduction</title>
<para>
Mono is an open source implementation of the Common Language Infrastructure
(CLI) specified in ECMA standard 335. It comes with a C# compiler and
provides an extensible platform to develop and run applications that
are interoperable with Microsoft .NET.
</para>
<para>
Mono is not finished--it is a project still under development. As a
result, installation and configuration may not be as smooth as you
will be used to from other Linux applications. Nevertheless, mono is
in a state that will allow you to get it up and running and gain
experience with it--which is, I would suggest, a very smart thing to do.
</para>
<para>
This document is limited in the following sense: it describes how to
download a 'stable' version of mono as a 'tarball' and get it to run on
your computer. I'm also assuming you run mono on Linux rather than
on Windows. All the examples have been tested on a 'vanilla' Red Hat 7.3
installation.
</para>
<para>
There are two items this document will <emphasis>not
</emphasis> cover: the first is how to self host the mcs compiler
under linux and the second is the graphical user environment
which is implemented as GTK#. These two interesting topics
are the subject of two more howto's that I'm planning.
</para>
<para>
This document is also less useful for two types of people.
</para>
<itemizedlist>
<listitem>
<para>
If you are a very inexperienced linux user and want to know what mono is
all about, there is an easier way to install mono. Go to mono.baselabs.org
and download the rpm's ready for installation on your system. This site also
runs a tutorial that is worth reading.
</para>
</listitem>
<listitem>
<para>
If you are a very experienced user wanting to contribute to the mono code,
you should probably regularly do a CVS download. At the moment, the mono
code grows very fast, and the 'stable' releases still appear too slowly.
</para>
</listitem>
</itemizedlist>
<para>
This document is aimed at the mono beginner, and aims to present a complete
view of a minimal installation, which will allow you to experiment with
mono to some degree. It also describes some of those experiments. We
expect that after reading this document you'll go on to do either of
two things:
</para>
<orderedlist>
<listitem>
<para>
Continue to contribute to the mono project in some shape or form. The
website has some ideas and suggestions under the heading 'Contributing'.
</para>
</listitem>
<listitem>
<para>
Continue to write applications that run in mono.
</para>
</listitem>
</orderedlist>
<para>
We hope this document will be useful to you in your first steps with mono.
Happy hacking!
</para>
<sect2 id="note">
<title>A note on the development of this document</title>
<para>
This document is expected to grow into a full 'running mono howto' over time.
As of yet, it does not really discuss some of the excellent efforts of others
to package mono into an rpm or deb and prepare it for easy installation.
It is our aim to include this in future versions of this document.
</para>
</sect2>
<sect2 id="prerequisites">
<title>Prerequisites</title>
<para>
This document assumes you are somewhat familiar with the architecture
of the Common Language Infrastructure and the C# programming language.
</para>
<para>
To compile mono on your system, you will also have to satisfy
some dependencies on other software. A list of these are given
on the mono download page. Read through this list to see if
you've got all components.
</para>
<para>
On a practical note, I had no dependency issues with the
installation of mono 0.12 on a 'standard issue' Red Hat 7.3 build.
</para>
</sect2>
<sect2 id="disclaimer"> <title>Disclaimer</title>
<para>
No liability for the contents of this document can be accepted.
Use the concepts, examples and information at your own risk. There may
be errors and inaccuracies, that could be damaging to your system.
Proceed with caution, and although this is highly unlikely, the author(s)
do not take any responsibility.
</para>
<para>
All copyrights are held by their by their respective owners,
unless specifically noted otherwise. Use of a term in this document
should not be regarded as affecting the validity of any trademark or
service mark. Naming of particular products or brands should not be
seen as endorsements.
</para>
</sect2>
<!-- Give credit where credit is due...very important --> <sect2
id="credits"> <title>Credits / Contributors</title>
<para> This document was originally created by Jaime Anguiano Olarra,
but has been extensively rewritten. Credits are due to </para>
<itemizedlist>
<listitem>
<para>Jaime Anguiano Olarra <email>jaime@geneura.ugr.es</email>
for creating the original version of this document, and in fact
the document that got me through installing mono for the first time.
</para>
</listitem>
<listitem>
<para>
My partner Margaret for support on my more exotic ventures.
</para>
</listitem>
</itemizedlist>
</sect2>
<!-- Feedback -->
<sect2 id="feedback"> <title>Feedback</title>
<para>
Feedback is most certainly welcome for this document. Send your
additions, comments and criticisms to the following email address:
<email>mono-docs-list@ximian.com</email>. I am lurking on this list
and will maintain this document as required.
</para>
</sect2>
</sect1>
<!-- This is the preamble stuff over with the rest of document
follows... -->
<sect1 id="installation">
<title> Installing Mono</title>
<sect2 id="obtaining">
<title>Obtaining Mono</title>
<para>
There are several ways to get Mono running on your computer. This
document will discuss only one of those: downloading the source tarball
and utilising the make utilities to get mono up and running. There is
only one mono package to worry about if you are just after a 'base' install
of mono: the mono runtime. This package, found under the name "mono-x.xx"
has got a compiled version of the compiler built in.
</para>
<para>
You'll be able to complete everything in this document if you just install
the runtime, but taking a look at the compiler package is well worth the
effort. The compiler is written in C# and is 'self hosting' which means it
is able to compile itself.
</para>
<para>
As of this moment, it is my understanding that there are still some issues
with the 'self hosting' bit of the compiler on linux, although this is
expected to work in later versions of mono. If you are just interested in
finding out how mono will work under linux, I would not worry about the
self-hosting bit for now. The self-hosting of the compiler will be the
topic of a future howto.
</para>
<para>
See <ulink url="http://www.go-mono.com/download">the mono download
site</ulink> for the source of the tarballs.
</para>
<para>
This page also lists the current versions of the software
mono depends on. Make sure that your system has all the
required versions, otherwise mono won't compile.
</para>
<para>
At a minimum for mono 0.12, you'll need to:
</para>
<itemizedlist>
<listitem>
<para>
download and install
<ulink url="http//www.freedesktop.org/software/pkgconfig">
pkg-config</ulink>.
</para>
</listitem>
<listitem>
<para>
download and install
<ulink url="ftp://ftp.gtk.org/pub/gtk/v1.3/glib-1.3.12.tar.gz">
glib 1.3</ulink>.
</para>
</listitem>
</itemizedlist>
<para>
Installing the tarballs is done via GNU autoconf and
automake. The general upshot of running autoconf and automake is that you
can type <command>./configure</command> and then <command> make</command>
to do the build.
Typing <command>make install</command> completes the installation of mono
on your system.
</para>
<para>
To build the mono runtime package, unzip the tarball to some useful
location. I tend to use <command>/usr/src</command> as the location,
but you could really do it anywhere. For the install process, it is
also a good idea to be 'root'. The installation process will shuttle
some executables into <command>/usr/local/bin</command> (more about
that later).
</para>
<para>
Unzipping the tarballs will have created two directories in <command>
/usr/src/</command>, one called something like mono-x.xx and the other
mcs-x.xx. The one called 'mono' is the runtime environment, and this contains
all that is initially needed to run mono and investigate its inner workings.
</para>
<para>
To start building the mono runtime, first type <command>./configure</command>.
You will see an output like this:
</para>
<programlisting>
[root@taurus mono-0.12]# ./configure
loading cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
snip ....
checking BASE_DEPENDENCIES_CFLAGS... -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
checking BASE_DEPENDENCIES_LIBS... -lglib-2.0
checking for GC_malloc in -lgc... (cached) no
configure: warning: Compiling mono without GC.
checking if off_t is 64 bits wide... no
checking if _FILE_OFFSET_BITS=64 gives 64 bit off_t... ok
snip ...
creating Makefile
creating mono/Makefile
creating mono/utils/Makefile
creating mono/metadata/Makefile
creating mono/dis/Makefile
creating mono/cil/Makefile
creating mono/arch/Makefile
creating mono/os/Makefile
creating mono/os/win32/Makefile
creating mono/os/unix/Makefile
creating mono/arch/x86/Makefile
creating mono/arch/ppc/Makefile
creating mono/arch/sparc/Makefile
creating mono/arch/arm/Makefile
creating mono/interpreter/Makefile
creating mono/tests/Makefile
creating mono/benchmark/Makefile
creating mono/monoburg/Makefile
creating mono/monograph/Makefile
creating mono/jit/Makefile
creating mono/io-layer/Makefile
creating mono/handles/Makefile
creating runtime/Makefile
creating scripts/Makefile
creating man/Makefile
creating doc/Makefile
creating docs/Makefile
creating config.h
config.h is unchanged
GC: auto
[root@taurus mono-0.12]#
</programlisting>
<para>
This means that the configure script has now created all the
makefiles necessary to complete the build on your system.
Note the "GC: auto" at the end of the list of commands.
GC stands for "garbage collection" and it
will be addressed in a later section of this document.
</para>
<para>
You are now ready to start the mono "build" process. To kick
this off, you can type <command>make</command> at the
command prompt. You'll see something like this:
</para>
<programlisting>
[root@taurus mono-0.12]# make
make all-recursive
make[1]: Entering directory `/usr/src/mono-0.12'
Making all in mono
make[2]: Entering directory `/usr/src/mono-0.12/mono'
Making all in utils
make[3]: Entering directory `/usr/src/mono-0.12/mono/utils'
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I../.. -I../../mono
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -Wall
-Wunused -Wmissing-prototypes -Wmissing-declarations
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs
-Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings
-c mono-hash.c
</programlisting>
<para>
and this will continue for a while. On my 1 GHz Duron with 256 MB of RAM the
total build process takes about three minutes. All the terrible flags after gcc
have essentially been set by the configure script and there is no need to worry
about these.
</para>
<para>
To finally install mono, you can type <command>make install</command>
to get a working version of mono. This command will copy the
scripts that run the executables to a place where the operating system
will be ale to find them. This location is <command>/usr/local/bin</command>
on my system.
</para>
</sect2>
<sect2 id="garbage_collection">
<title> Garbage Collection</title>
<para>
To make the mint interpreter work with garbage collection, you first need to
install a garbage collection package on your system. Mono works with
Boehm Garbage collection, which is found at
<ulink url="http://www.hpl.hp.com/personal/Hans_Boehm/gc/">
http://www.hpl.hp.com/personal/Hans_Boehm/gc/
</ulink>.
</para>
<para>
To get garbage collection to work, I downloaded the source tarball
into <command>/usr/src/</command> and typed <command>./configure</command>
followed by <command>make</command> and <command>make install</command>.
</para>
<para>
There is one glitch to work around. The header file for the garbage collection
<command>gc.h</command> is found in the <command>/usr/src/gc6.0/include
</command> directory (at least on my system). The mono build process will break
on this location: it is looking for the header file in some other place called
<command>/usr/include/gc/</command> and won't be able to find the correct
header file.
</para>
<para>
The solution is to build a symbolic link between these two locations as
follows
</para>
<programlisting>
[root@taurus include]# ln -s /usr/src/gc6.0/include/ /usr/include/gc
</programlisting>
<para>
after which you'll be able to list the directory contents as if they were
in <command>/usr/include</command>
</para>
<programlisting>
[root@taurus include]# pwd
/usr/include
[root@taurus include]# ls /usr/include/gc
cord.h gc_backptr.h gc_inline.h javaxfc.h
ec.h gc_cpp.h gc_local_alloc.h leak_detector.h
gc gc_gcj.h gc_mark.h new_gc_alloc.h
gc_alloc.h gc.h gc_pthread_redirects.h private
gc_amiga_redirects.h gc_inl.h gc_typed.h weakpointer.h
[root@taurus include]#
</programlisting>
<para>
To get mono to work with garbage collection, you'll have to rebuild the
environment. This is done easily by typing <command>make distclean</command>
to clean up any existing executables.
</para>
<para>
Continue the build by typing <command>./configure</command>, and look at
the last line. It should read:
</para>
<programlisting>
snip...
creating config.h
GC: boehm
[root@taurus mono-0.12]#
</programlisting>
<para>
The GC: boehm tells you that garbage collection has been turned on. Now to
compile the runtime, you type <command>make</command> and <command> make
install</command> as previously.
</para>
<para>
You now have mono working with Garbage Collection.
</para>
<para>
Although my experimentation is incomplete as of this time, I have found some
issues with running Garbage Collection continuously, and my recommendation
would be to turn it off for now.
</para>
<para>
To turn garbage collection off again, you have to go to the <command>/usr/src
</command> directory where you extracted the tarball. Enter the <command>gc6.0
</command> directory and type <command>make uninstall</command> to uninstall
Garbage Collection. Then in your <command>mono</command> directory, type
<command>make distclean</command> followed by <command>./configure</command>,
<command>make</command> and <command>make install</command>.
</para>
</sect2>
</sect1>
<sect1 id="running">
<title>Running mono</title>
<sect2 id="basic">
<title>Basic steps</title>
<para>
To work with mono, you first have to create a C# program. Open up
your favourite editor, and type in the following code:
</para>
<programlisting>
using System;
class Hello
{
public static void Main(String[] args)
{
Console.WriteLine("mono:: is alive and well...");
for (int i = 0; i < args.Length; i++)
Console.WriteLine("Argument {0} = {1}", i, args[i]);
}
}
</programlisting>
<para>
Save the file as hello.cs. To compile this into a working program,
type mcs hello.cs. If you get the following:
</para>
<programlisting>
[hinne@taurus hello]$ mcs hello.cs
RESULT: 0
[hinne@taurus hello]$
</programlisting>
<para>
you know the compile worked fine. If you see some strange error
messages including the word 'parser' somewhere, you made a mistake in
your program. Fix this up first.
</para>
<para>
You are now ready to execute your first mono program. To execute
the code, type
</para>
<programlisting>
[hinne@taurus hello]$ mono hello.exe arg1 arg2 arg 3
</programlisting>
<para>
(where we have given some arguments just for fun) and you'll
see the following:
</para>
<programlisting>
mono:: is alive and well...
Argument 0 = arg1
Argument 1 = arg2
Argument 2 = arg
Argument 3 = 3
RESULT: 0
</programlisting>
<para>
As you can see, mono printed the line "mono:: is alive and well"
and printed the list of arguments. This completes the creation
and execution of your first mono program.
</para>
</sect2>
<sect2 id="interpreter">
<title>Interpreter</title>
<para>
But mono will allow you to do more. First of all, mono is the
compiled mono execution environment which uses the Just in
Time (JIT) compiler. Mono also comes with an interpreted
environment, which can be accessed using the command 'mint'
as follows
</para>
<programlisting>
[hinne@taurus hello]$ mint hello.exe arg1 arg 2
mono:: is alive and well...
Argument 0 = arg1
Argument 1 = arg
Argument 2 = 2
[hinne@taurus hello]$
</programlisting>
<para>
As you can see, it makes no difference to mono output which
environment you use, but what happens under the hood is very
different. If you use 'mono' as the command line tool, you
call the 'production' execution environment which will read
your portable executable (PE) file, and call the just in
time (JIT) compiler to compile the PE code down to machine
level code (in my case, an x86 architecture) after which
it is executed.
</para>
<para>
If you use mint, the JIT is not used, and the PE code is
interpreted into x86 instructions for execution. In fact,
for our simple 'hello' mint is slightly faster. The point
is that the JIT compiler will take some time to compile the
code of our program and store it in some location in memory,
but the subsequent execution of the code is faster with mono.
</para>
<para>
You can see what happens below (the thing to look for is the
'user' time: 0.1 seconds with mono and 0.06 seconds with mint):
</para>
<programlisting>
[hinne@taurus hello]$ time mono hello.exe arg1 arg 2
mono:: is alive and well...
Argument 0 = arg1
Argument 1 = arg
Argument 2 = 2
RESULT: 0
real 0m0.575s
user 0m0.100s
sys 0m0.010s
[hinne@taurus hello]$ time mint hello.exe arg1 arg 2
mono:: is alive and well...
Argument 0 = arg1
Argument 1 = arg
Argument 2 = 2
real 0m0.545s
user 0m0.060s
sys 0m0.000s
[hinne@taurus hello]$
</programlisting>
<para>
After this simple run of mono, it is time to play with some options.
I won't cover these in detail since there are quite a few, and also because
I assume you downloaded mono to hack it around in the first place. So
I'll leave some pointers.
</para>
<sect3 id="debugging">
<title>Debugging</title>
<para>
Mono supports a debugging option when you specify the "-d" flag while running
the runtime. Utilising this flag will get you a significant amount of output,
and it may be an idea to specify an output file as well. The interesting aspect
of this file is that it allows you to see to some extent (quite precisely,
actually) what the JIT compiler is up to.
</para>
</sect3>
<sect3 id="statistics">
<title>Statistics</title>
<para>
It is also possible to collect some runtime statistics on your program. These
will give you some idea of the resource utilisation of your program.
</para>
<programlisting>
[hinne@taurus hello]$ mono --stats hello.exe
mono:: is alive and well...
RESULT: 0
Mono Jit statistics
Compiled methods: 58
Methods cache lookup: 15
Method trampolines: 698
Basic blocks: 188
Max basic blocks: 15
Allocated vars: 238
Analyze stack repeat: 61
Compiled CIL code size: 2450
Native code size: 10167
Max code size ratio: 7.13 (FileStream::FlushBuffer)
Biggest method: 1016 (StreamWriter::Write)
Code reallocs: 27
Allocated code size: 22073
Inlineable methods: 17
Inlined methods: 22
Created object count: 18
Initialized classes: 127
Used classes: 37
Static data size: 288
VTable data size: 8292
</programlisting>
</sect3>
</sect2>
<sect2 id="ILAsm_code" >
<title>Inspecting IL Assembly code</title>
<para>
Mono also provides a small tool that will let you disassemble
the executable (.exe) file so you can have a peek
under the hood. This tool is monodis, and is run as
follows:
</para>
<programlisting>
[hinne@taurus hello]$ monodis hello.exe
.assembly extern mscorlib
{
.ver 0:0:0:0
}
.assembly 'hello'
{
.hash algorithm 0x00008004
.ver 0:0:0:0
}
.class private auto ansi beforefieldinit Hello
extends [mscorlib]System.Object
{
// method line 1
.method public hidebysig specialname rtspecialname
instance default void .ctor() cil managed
{
// Method begins at RVA 0x20ec
// Code size 7 (0x7)
.maxstack 8
IL_0000: ldarg.0
IL_0001: call instance void System.Object::.ctor()
IL_0006: ret
} // end of method instance default void .ctor()
// method line 2
.method public static
default void Main(string[] args) cil managed
{
// Method begins at RVA 0x20f4
.entrypoint
// Code size 56 (0x38)
.maxstack 5
.locals init (
int32 V_0,
int32 V_1)
IL_0000: ldstr "mono:: is alive and well..."
IL_0005: call void System.Console::WriteLine(string)
IL_000a: ldc.i4.0
IL_000b: stloc.0
IL_000c: ldloc.0
IL_000d: ldarg.s 0
IL_000f: ldlen
IL_0010: clt
IL_0012: brfalse IL_0037
IL_0017: ldstr "Argument {0} = {1}"
IL_001c: ldloc.0
IL_001d: box [mscorlib]System.Int32
IL_0022: ldarg.s 0
IL_0024: ldloc.0
IL_0025: ldelem.ref
IL_0026: call void System.Console::WriteLine(string, object, object)
IL_002b: nop
IL_002c: ldloc.0
IL_002d: ldc.i4.1
IL_002e: add
IL_002f: stloc.1
IL_0030: ldloc.1
IL_0031: stloc.0
IL_0032: br IL_000c
IL_0037: ret
} // end of method default void Main(string[] args)
} // end of type Hello
[hinne@taurus hello]$
</programlisting>
<para>
This is the listing of the code of your program in a language
called IL assembly, or Common Intermediate Language (CIL). The
CIL provides the portability of the mono platform, and ensures
that code compiled with Microsoft's .NET framework will work
on mono and vice versa.
</para>
</sect2>
<sect2 id="man_pages">
<title>Man pages</title>
<para>
Mono has man pages already installed, and generally, typing <command>
man</command> before the command you wish to execute should help in
getting a list of the options. In many cases, it's still up to you
to figure out what they do.
</para>
</sect2>
</sect1>
<sect1 id="problems">
<title>Problems</title>
<para>
With mono being as new as it is, it is likely that you will have some
problems with installation. The following are some ideas to help you
out in a bind:
</para>
<orderedlist>
<listitem>
<para>
See the Ximian Bugzilla page to find out if there is a bug
report about your specific issue.
</para>
</listitem>
<listitem>
<para>Read this document. If it does not solve your problem, we want to
know about it. Please send a message to the email address listed for
feedback at the beginning of the document.</para>
</listitem>
<listitem>
<para>
Visit the mono mailing lists' archives and do a little
research in there for threads talking about the problem you have.
</para>
</listitem>
<listitem>
<para>
If you still cannot correct the problem, send a message to the
mono list. When you do this, please be as precise as possible--i.e.
mention the system you are running, the version of mono that you have the
problem with, and give any error codes and other output that might appear.
</para>
</listitem>
</orderedlist>
</sect1>
<sect1 id="knownproblems">
<title>Known Problems</title>
<para> mcs fails to compile in Linux.
To the best of my knowledge, as of yet mcs cannot compile in Linux.
Try to install the already made packages from
http://mono.baselabs.org/index.php/software. </para>
</sect1>
<!-- Legal Sections --> <sect1 id="copyright">
<title>Copyright and License</title>
<!-- The LDP recommends, but doesn't require, the GFDL --> <para>
This document, <emphasis>Running mono</emphasis>, is copyrighted
(c) 2002 by <emphasis>Hinne Hettema</emphasis> and
<emphasis>Jaime Anguiano Olarra</emphasis>. Permission is
granted to copy, distribute and/or modify this document under the
terms of the GNU Free Documentation License, Version 1.1 or any later
version published by the Free Software Foundation; with no Invariant
Sections, with no Front-Cover Texts, and with no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU Free
Documentation License".
</para>
<sect2 id="gfdl"> <title>GNU Free Documentation License</title>
<!-- GNU Project - Free Software Foundation (FSF) -->
<para>Version 1.1, March 2000</para>
<blockquote> <para>Copyright (C) 2000 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is
permitted to copy and distribute verbatim copies of this license document,
but changing it is not allowed.</para> </blockquote>
<sect3 id="gfdl-0"> <title>PREAMBLE</title>
<para>The purpose of this License is to make a manual, textbook,
or other written document "free" in the sense of freedom: to assure
everyone the effective freedom to copy and redistribute it, with
or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher
a way to get credit for their work, while not being considered
responsible for modifications made by others.</para>
<para>This License is a kind of "copyleft", which means that
derivative works of the document must themselves be free in the
same sense. It complements the GNU General Public License, which
is a copyleft license designed for free software.</para>
<para>We have designed this License in order to use it for manuals
for free software, because free software needs free documentation:
a free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to software
manuals; it can be used for any textual work, regardless of subject
matter or whether it is published as a printed book. We recommend
this License principally for works whose purpose is instruction
or reference.</para>
</sect3>
<sect3 id="gfdl-1"> <title>APPLICABILITY AND DEFINITIONS</title>
<para>This License applies to any manual or other work that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. The "Document", below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as "you".</para>
<para>A "Modified Version" of the Document means any work
containing the Document or a portion of it, either copied verbatim,
or with modifications and/or translated into another language.</para>
<para>A "Secondary Section" is a named appendix or a front-matter
section of the Document that deals exclusively with the relationship
of the publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (For example, if the Document
is in part a textbook of mathematics, a Secondary Section may not
explain any mathematics.) The relationship could be a matter of
historical connection with the subject or with related matters, or
of legal, commercial, philosophical, ethical or political position
regarding them.</para>
<para>The "Invariant Sections" are certain Secondary Sections
whose titles are designated, as being those of Invariant Sections,
in the notice that says that the Document is released under this
License.</para>
<para>The "Cover Texts" are certain short passages of text that
are listed, as Front-Cover Texts or Back-Cover Texts, in the notice
that says that the Document is released under this License.</para>
<para>A "Transparent" copy of the Document means a
machine-readable copy, represented in a format whose specification
is available to the general public, whose contents can be viewed and
edited directly and straightforwardly with generic text editors
or (for images composed of pixels) generic paint programs or
(for drawings) some widely available drawing editor, and that is
suitable for input to text formatters or for automatic translation
to a variety of formats suitable for input to text formatters.
A copy made in an otherwise Transparent file format whose markup
has been designed to thwart or discourage subsequent modification
by readers is not Transparent. A copy that is not "Transparent"
is called "Opaque".</para>
<para>Examples of suitable formats for Transparent copies include
plain ASCII without markup, Texinfo input format, LaTeX input format,
SGML or XML using a publicly available DTD, and standard-conforming
simple HTML designed for human modification. Opaque formats include
PostScript, PDF, proprietary formats that can be read and edited
only by proprietary word processors, SGML or XML for which the
DTD and/or processing tools are not generally available, and the
machine-generated HTML produced by some word processors for output
purposes only.</para>
<para>The "Title Page" means, for a printed book, the title page
itself, plus such following pages as are needed to hold, legibly,
the material this License requires to appear in the title page.
For works in formats which do not have any title page as such,
"Title Page" means the text near the most prominent appearance of the
work's title, preceding the beginning of the body of the text.</para>
</sect3>
<sect3 id="gfdl-2"> <title>VERBATIM COPYING</title>
<para>You may copy and distribute the Document in any medium,
either commercially or noncommercially, provided that this License,
the copyright notices, and the license notice saying this License
applies to the Document are reproduced in all copies, and that
you add no other conditions whatsoever to those of this License.
You may not use technical measures to obstruct or control the
reading or further copying of the copies you make or distribute.
However, you may accept compensation in exchange for copies. If you
distribute a large enough number of copies you must also follow the
conditions in section 3.</para>
<para>You may also lend copies, under the same conditions stated
above, and you may publicly display copies.</para>
</sect3>
<sect3 id="gfdl-3"> <title>COPYING IN QUANTITY</title>
<para>If you publish printed copies of the Document numbering more
than 100, and the Document's license notice requires Cover Texts, you
must enclose the copies in covers that carry, clearly and legibly,
all these Cover Texts: Front-Cover Texts on the front cover, and