<div>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. </div>
<div class="mailbox_signature">—<br>Sent from <a href="https://www.dropbox.com/mailbox">Mailbox</a> for iPhone</div>
<br><br><div class="gmail_quote"><p>On Wed, Oct 30, 2013 at 11:08 PM, Olaf Ryder <span dir="ltr"><<a href="mailto:devbits01@gmail.com" target="_blank">devbits01@gmail.com</a>></span> wrote:<br></p><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div dir="ltr">Greetings,<div><br></div>
<div>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.</div>
<div><br></div>
<div>1) What exactly is happening during the Experimental build step? </div>
<div>2) How does CTest know what targets to build within a complex project?</div>
<div>3) Is there a way to get verbose output of what's going on during the various steps?</div>
<div><br></div>
<div>Thank you</div>
<div><div>
<br></div></div>
</div></blockquote></div><br>