Bug 33388 - xbuild v12 does not recognise /m parameter
Summary: xbuild v12 does not recognise /m parameter
Status: NEW
Alias: None
Product: Tools
Classification: Mono
Component: xbuild ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-08-26 04:44 UTC by Paul D'Ambra
Modified: 2015-08-26 04:44 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 33388 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Paul D'Ambra 2015-08-26 04:44:40 UTC
I tried to use xbuild to run a command a had been using with xbuild

msbuild /verbosity:normal /property:configuration="Release" /property:VisualStudioVersion="12.0" /m /property:RunOctoPack="true" /property:OctoPackEnforceAddingFiles="true" /target:"Clean" ../MYSLN.sln


xbuild /verbosity:normal /property:configuration="Release" /property:VisualStudioVersion="12.0" /m /property:RunOctoPack="true" /property:OctoPackEnforceAddingFiles="true" /target:"Clean" ../MYSLN.sln

this reported: MSBUILD: error MSBUILD0004: Too many project files specified

I tracked that error down to https://github.com/mono/mono/blob/master/mcs/tools/xbuild/Parameters.cs#L77 and started writing a test.

That showed that the /m parameter wasn't recognised by xbuild.

/m is documented here: https://msdn.microsoft.com/en-us/library/ms164311.aspx

for completeness I'll include the text (As I can't link to the item on the page)

Specifies the maximum number of concurrent processes to use when building. If you don't include this switch, the default value is 1. If you include this switch without specifying a value, MSBuild will use up to the number of processors in the computer. For more information, see Building Multiple Projects in Parallel with MSBuild.
The following example instructs MSBuild to build using three MSBuild processes, which allows three projects to build at the same time:
msbuild myproject.proj /maxcpucount:3

Should this be supported?