[cmake-developers] [PATCH] ExternalProject: Added new USES_TERMINAL options

James Johnston johnstonj.public at codenest.com
Mon Jul 6 01:52:34 EDT 2015


Hi,

I worked on a patch to allow you to pass USES_TERMINAL through
ExternalProject to the underlying add_custom_command().  Here is the commit
message:

ExternalProject:  Added new USES_TERMINAL options

Added new USES_TERMINAL option to the ExternalProject_Add_Step
function.  This option passes USES_TERMINAL to the underlying
add_custom_command call so that the Ninja console pool is used.
Also, corresponding new USES_TERMINAL_<step> options were added
to the ExternalProject_Add function.

Justification: if using Ninja with a CMake superbuild, it's often
desirable to limit the superbuild to ONE sub-Ninja process at a
time to avoid oversubscribing the CPU.  Using the console pool also
makes it easy to monitor the progress of the sub-Ninja process.

Independent USES_TERMINAL_<step> arguments are passed to
ExternalProject_Add instead of one USES_TERMINAL argument that
controls everything.  Users may wish to run some steps in parallel
but not others (e.g. parallelize configure but not build).

Best regards,

James Johnston
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-ExternalProject-Added-new-USES_TERMINAL-options.patch
Type: application/octet-stream
Size: 13915 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20150706/05fbd7e7/attachment.obj>


More information about the cmake-developers mailing list