Can't get NEW CMP0147 (BuildInParallel) to work

Usage
, ,
1

I’m generating projects for Visual Studio 2022.
I upgraded my CMake.exe to version 3.30.2.
Then I bumped my cmake_minimum_required to 3.30.
I also added cmake_policy(SET CMP0147 NEW) a couple of times into my top-level CMakeLists.txt.

I now expected that the BuildInParallel flag is set to true for all add_custom_command calls. However, there is exactly one, which is in the ZERO_CHECK project. Everything else does not use this flag.

Is there anything else that I’m missing? From the documentation it seems like just setting the policy to NEW should do the trick.

See policy docs here: https://cmake.org/cmake/help/latest/policy/CMP0147.html#policy:CMP0147
And release notes for 3.27 here: https://cmake.org/cmake/help/latest/release/3.27.html#other-changes

2

Use the Ninja generator if you want really parallel builds!

3

Can you please provide a small test project that shows the problem?

4

Hello @ben.boeckel,

Not OP, but I have an example here GitHub - noahwhygodwhy/BuildInParallelCMakeExample: BuildInParallelCMakeExample

It doesn’t actually demonstrate the hit to performance due to BuildInParallel that I’m seeing on the full project, but it does demonstrate that the BuildInParallel flag on the custom target RunAllPythonScripts doesn’t get set (which does cause a significant performance gap on the full project)

Project configured and generated using all defaults using cmakegui 4.1.0rc3, targeting visualstudio 17 2022 and msvc.

Please let me know if there’s any other information you need or anything I can help with. Being able to automatically set that setting on cmake generated visual studio projects would be huge for the team i’m on.

Also ninja isn’t currently an option for us currently due to certain factors