On Sat, Mar 28, 2015 at 10:38 AM, Taylor Braun-Jones <tay...@braun-jones.org> wrote: > > See htop screenshot below for an example of what I mean. Note that `ninja` in the original command line invocation is just a bash alias for ninja-build (the name of the ninja binary on Fedora-based systems) > > Should I expect to see the -l3 option to be propagated automatically to the sub projects of my superbuild? Or do I need to do some special cmake configuration to make this happen? Or is this just a known issue?
I'm still seeing this behavior with CMake 3.4.1. Here's a friendlier plaintext representation of the previous htop screenshot snippet: ninja -l3 └── /usr/bin/ninja-build ├── /usr/bin/ninja-build └── /usr/bin/ninja-build Is this expected behavior, a known bug, or a new bug that I should file? Note that this example shows the -l option not being propagated, but I think all of the following Ninja options should be propagated: -l N do not start new jobs if the load average is greater than N -n dry run (don't run commands but act like they succeeded) -v show all command lines while building -d stats print operation counts/timing info -d explain explain what caused a command to execute -t clean clean built files -t commands list all commands required to rebuild given targets Thanks, Taylor
-- 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