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 <[email protected]> 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
--
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://www.cmake.org/mailman/listinfo/cmake
