On 2017-08-21 14:55, Cantor, Scott wrote:
Primarily a Windows thing, my colleague doing testing says he doesn't
think the default build currently spawns muiltiple threads inside the
VS builds unless he turns that on. Is there a reason not to turn it on
by default in the CMakeFile.txt file?
What type of change is your colleague proposing to turn it on?
Have they read
https://blog.kitware.com/cmake-building-with-all-your-cores/ ? There
are some caveats there which are worth noting (relating to /MP) which
make adding it by default potentially bad since in combination with
target-level parallelism it can greatly exceed the resources of the
machine and break the build. It's also quite possible that xerces is
already being built in parallel with other projects [we do this] so
enabling parallelisation at the lowest level can break the
parallelisation already in place at a much higher level. There are also
multiple ways to parallelise builds on Windows, so any change should not
compromise building with any of the other methods.
If there's a way of safely enabling it, that would be great, but it
appears the current recommendations are to configure this when running
cmake rather than hardcoding the behaviour.
Kind regards,
Roger
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
