[CMake] CTest - Speed Optimization

Leif Walsh leif.walsh at gmail.com
Thu Oct 31 00:03:42 EDT 2013


It builds everything using "cmake --build ." I believe, or something very similar to that. It doesn't guess at what to build, it just builds everything. This is slow with make at least because it's single threaded. To do a parallel build, you can build (make -jN) right before you run ctest, in order to make the build phase of ctest a no-op, or you can use a generator that uses parallel build by default, like the Ninja generator. 

—
Sent from Mailbox for iPhone

On Wed, Oct 30, 2013 at 11:08 PM, Olaf Ryder <devbits01 at gmail.com> wrote:

> Greetings,
> I'm looking for ways to speed up CTest runs (the Experimental target). It
> would appear the majority of the time is spent during the build step.
> 1) What exactly is happening during the Experimental build step?
> 2) How does CTest know what targets to build within a complex project?
> 3) Is there a way to get verbose output of what's going on during the
> various steps?
> Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20131030/810231ca/attachment.htm>


More information about the CMake mailing list