global.conf
Warning
This new configuration mechanism is an experimental feature subject to breaking changes in future releases.
The global.conf file is located in the Conan user home directory.
Global configuration
core:required_conan_version = "expression"allows defining a version expression like “>=1.30”. Conan will raise an error if its current version does not satisfy the conditioncore.package_id:msvc_visual_incompatibleallows opting-out the fallback from the newmsvccompiler to theVisual Studiocompiler existing binaries
Tools configurations
Tools and user configurations allows them to be defined both in the global.conf file and in profile files. Profile values will have priority over globally defined ones in global.conf, and can be defined as:
[settings]
...
[conf]
tools.microsoft.msbuild:verbosity=Diagnostic
tools.microsoft.msbuild:max_cpu_count=20
tools.microsoft.msbuild:vs_version = 16
tools.build:processes=10
tools.ninja:jobs=30
tools.gnu.make:jobs=40
Existing configurations:
tools.microsoft.msbuild:verbosityallows defining a value from"Quiet", "Minimal", "Normal", "Detailed", "Diagnostic"for build using the MSBuild system, it could be with thetools.microsoft.MSBuildor with thetools.cmake.CMakehelpers.tools.microsoft.msbuild:max_cpu_countargument for the/m(/maxCpuCount) when runningMSBuildstandalone or via CMake (overrides the generaltools.build:processes).tools.microsoft.msbuild:vs_versiondefines the compiler version when using using the newmsvccompiler.tools.build:processes: number of processes to use for every build-helper.tools.ninja:jobsargument for the--jobsparameter when running Ninja generator via CMake or Meson. (overrides the generaltools.build:processes).tools.gnu.make:jobs: argument for the--jobsparameter when runningmake(overrides the generaltools.build:processes).
To list all possible configurations available, run conan config list.