max_cpu_count (#3926)

conan-io · Dec 2, 2024 · b3912c0 · b3912c0
1 parent 49c0228
commit b3912c0
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/reference/tools/cmake/cmake.rst b/reference/tools/cmake/cmake.rst
@@ -61,7 +61,7 @@ The ``CMake()`` build helper is affected by these ``[conf]`` variables:
 - ``tools.build:jobs`` argument for the ``--jobs`` parameter when running Ninja generator.
 
 - ``tools.microsoft.msbuild:max_cpu_count`` argument for the ``/m`` (``/maxCpuCount``) when running
-  ``MSBuild``
+  ``MSBuild``. If ``max_cpu_count=0``, then it will use ``/m`` without arguments, which means use all available cpus.
 
 - ``tools.cmake:cmake_program`` specify the location of the CMake executable, instead of using the one found in the ``PATH``.
 

diff --git a/reference/tools/microsoft/msbuild.rst b/reference/tools/microsoft/msbuild.rst
@@ -72,7 +72,7 @@ conf
 - ``tools.build:verbosity`` accepts one of ``quiet`` or ``verbose`` to be passed
   to the ``MSBuild.build()`` call as ``msbuild .... /verbosity:{Quiet,Detailed}``.
 - ``tools.microsoft.msbuild:max_cpu_count`` maximum number of CPUs to be passed to the ``MSBuild.build()``
-  call as ``msbuild .... /m:N``.
+  call as ``msbuild .... /m:N``. If ``max_cpu_count=0``, then it will use ``/m`` without arguments, which means use all available cpus.