One of the VTK dashboards does it by giving a custom MAKECOMMAND to the initial cache:<div>MAKECOMMAND:STRING=/usr/bin/make -i -j 2</div><div><br class="webkit-block-placeholder"></div><div>See here for the full script:</div>
<div><a href="http://www.vtk.org/Testing/Sites/hythloth.kitware/Linux-gcc41/20080215-0300-Nightly/Notes.html">http://www.vtk.org/Testing/Sites/hythloth.kitware/Linux-gcc41/20080215-0300-Nightly/Notes.html</a></div><div><br class="webkit-block-placeholder">
</div><div><br>HTH,</div><div>David</div><div><br class="webkit-block-placeholder"></div><div><br><div><span class="gmail_quote">On 2/15/08, <b class="gmail_sendername">James Bigler</b> <<a href="mailto:bigler@cs.utah.edu">bigler@cs.utah.edu</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
Is it possible to get ctest to do parallel builds on systems that support it?<br> <br> I'm using a configuration file that looks something like this:<br> <br> # Where the source code lives<br> SET (CTEST_SOURCE_DIRECTORY "${CTEST_SCRIPT_DIRECTORY}/..")<br>
SET (CTEST_BINARY_DIRECTORY "${CTEST_SOURCE_DIRECTORY}/build-ctest-sse")<br> <br> # Make sure we always reconfigure cmake stuff from scratch and don't<br> # rely on previously built libraries<br> SET (CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE)<br>
<br> SET (CTEST_CMAKE_COMMAND "cmake")<br> SET (CTEST_CVS_COMMAND "svn")<br> <br> # A smoke test only builds the code and doesn't run any tests, so we<br> # exclude all tests here<br> #SET (CTEST_COMMAND "ctest -D Nightly")<br>
SET (CTEST_COMMAND "ctest -D Experimental")<br> <br> SET(CTEST_INITIAL_CACHE "<br> BUILDNAME:STRING=SSE<br> BUILD_TESTING:BOOL=ON<br> ")<br> <br> <br> James<br> _______________________________________________<br>
CMake mailing list<br> <a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br> <a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a><br> </blockquote></div><br> </div>