On 01/30/2017 02:26 PM, Dave Flogeras wrote:

On Sun, Jan 29, 2017 at 9:53 AM, Nils Gladitz <nilsglad...@gmail.com <mailto:nilsglad...@gmail.com>> wrote:

    FWIW I don't think -j does anything when you build the
    NightlyBuild target given that that make invocation is not the one
    directly performing the actual build.
    The only command being run by the NightlyBuild target would be
    "ctest -D NightlyBuild" (nothing to parallelize when there is only
    one command).
    CTest would spawn another make process for the build.

    Nils


Good point, I checked with the older version of make (4.1) and even though it doesn't issue the warning, it is not building my project in parallel.

I guess that brings up the obvious question: how does one use this target and take advantage of multiple processors? Basically, I'm calling it within a python loop that permutes various projects and configurations (release/debug/shared/static...) then puts the results on a self-hosted CDash server with make NightlySubmit.

I don't know how to do this with the generic dashboard targets ... assuming no one else does either you could give CTest script mode a try (ctest -S). In script mode the ctest_build() command has a FLAGS option which takes build tool specific options like -j.

Nils
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Reply via email to