From f85048dd2127a5e90e5bbfdc7de68a61143ceb28 Mon Sep 17 00:00:00 2001 From: Miguel de Icaza Date: Thu, 13 May 2004 20:24:49 +0000 Subject: [PATCH] Flush svn path=/trunk/mono/; revision=27308 --- man/mcs.1 | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/man/mcs.1 b/man/mcs.1 index 688f899a0e5..9183aca5daf 100755 --- 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