2004-05-29 Gonzalo Paniagua Javier <gonzalo@ximian.com>

[mono.git] / man / mcs.1

diff --git a/man/mcs.1 b/man/mcs.1
index 688f899a0e5534701088c3bfd1df32f43755f5a8..9183aca5daf1192326999381379592e3fdf8e53e 100755 (executable)
--- a/man/mcs.1
+++ b/man/mcs.1
@@ -108,10 +108,6 @@ key containers. The option is equivalent to including [assembly:
 AssemblyKeyName ("CONTAINER")] in your source code. Compiler option 
 takes precedence over the attributes.
 .TP
-.I \-\-stacktrace
-Generates a stack trace at the time the error is reported, useful for
-debugging the compiler.
-.TP
 .I -lib:PATHLIST
 Each path specified in the comma-separated list will direct the
 compiler to look for libraries in that specified path.
@@ -142,6 +138,16 @@ Names the output file to be generated.
 .I \-\-parse
 Used for benchmarking.  The compiler will only parse its input files.
 .TP
+.I \-pkg:package1[,packageN]
+The compiler will invoke pkg-config --libs on the set of packages
+specified on the command line to obtain libraries and directories to
+compile the code.
+.PP
+This is typically used with third party components, like this:
+.nf
+               $ mcs -pkg:gtk-sharp demo.cs
+.fi
+.TP
 .I -resource:RESOURCE[,ID]
 Embeds to the given resource file.  The optional ID can be used to
 give a different name to the resource.  If not specified, the resource
@@ -165,9 +171,13 @@ Does recursive compilation using the specified pattern.  In Unix the
 shell will perform globbing, so you migth want to use it like this:
 .PP
 .nf
-               bash$ mcs -recurse:'*.cs' 
+               $ mcs -recurse:'*.cs' 
 .fi
 .TP
+.I \-\-stacktrace
+Generates a stack trace at the time the error is reported, useful for
+debugging the compiler.
+.TP
 .I \-target:KIND, \-t:KIND
 Used to specify the desired target.  The possible values are: exe
 (plain executable), winexe (Windows.Forms executable), library