.B \//logger:<logger>
Custom logger to log build events
.TP
+.B \//toolsversion:version , /tv:version
+Specify the toolset version to use.
+
+Eg. /tv:4.0
+ This would cause 4.0 version of the Microsoft.Common.targets (among others) to be used. This overrides
+ the value specified in a project file.
+
+Valid values: 2.0, 3.0, 3.5 and 4.0
+.TP
.B \//verbosity:<level>
Logger verbosity level : quiet, minimal, normal, detailed, diagnostic
.TP
MSBuild extensions are usually installed in $(MSBuildExtensionsPath), which xbuild resolves
to $prefix/lib/mono/xbuild . When used in Import, like:
- <Import Project="$(MSBuildExtensionsPath)\TestTargets.targets"/>
+ <Import Project="$(MSBuildExtensionsPath)\\TestTargets.targets"/>
xbuild tries various values for the msbuild property $(MSBuildExtensionsPath), in order:
1. Paths specified in the environment variable $MSBuildExtensionsPath.
- 2. $XDG_CONFIG_HOME/xbuild/tasks (or Environment.SpecialFolder.ApplicationData)
- 3. $prefix/lib/mono/xbuild (default location)
+ 2. /Library/Frameworks/Mono.framework/External/xbuild on Mac OSX.
+ 3. $XDG_CONFIG_HOME/xbuild/tasks (or Environment.SpecialFolder.ApplicationData)
+ 4. $prefix/lib/mono/xbuild (default location)
Anywhere else in the project files, $(MSBuildExtensionsPath) will always resolve to the default
location. This is a xbuild-only feature.
+This is also applicable for the properties $(MSBuildExtensionsPath32) and $(MSBuildExtensionsPath64),
+and the environment variables have the corresponding names - MSBuildExtensionsPath32/64 .
.TP
.I "XBUILD_COLORS"
If this variable is set, it contains a string of the form
You can disable the built-in color scheme by setting this variable to
"disable".
+.SH NOTES
+On Mac OSX, for locating pkg-config (.pc) files, xbuild additionally
+looks in "/Library/Frameworks/Mono.framework/External/pkgconfig" .
+
.SH SEE ALSO
.BR mono(1), mcs(1)
.SH COPYRIGHT