<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>ctest has long been quite "under-documented"</div><div><br></div><div>There are some open issues in the bug tracker:</div><div><br></div><div> <span style="font-family: '.HelveticaNeueUI'; font-size: 15px; line-height: 19px; white-space: nowrap; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); -webkit-text-size-adjust: none; "><a href="http://public.kitware.com/Bug/view.php?id=10392">http://public.kitware.com/Bug/view.php?id=10392</a></span></div><div><span style="font-family: '.HelveticaNeueUI'; font-size: 15px; line-height: 19px; white-space: nowrap; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); -webkit-text-size-adjust: none; "> </span><span style="font-family: '.HelveticaNeueUI'; font-size: 15px; line-height: 19px; white-space: nowrap; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); -webkit-text-size-adjust: none; "><a href="http://public.kitware.com/Bug/view.php?id=13836">http://public.kitware.com/Bug/view.php?id=13836</a></span></div><div><br></div><div>What's needed is someone to go in and do the work to document it well.</div><div><br></div><div>Until that happens, your best bet is to ask specific questions here to fill in the gaps...</div><div><br></div><div><br></div><div>HTH,</div><div>David C</div><div><br></div><div><br></div><div>On Apr 10, 2013, at 10:09 AM, Martin Baute <<a href="mailto:solar@rootdirectory.de">solar@rootdirectory.de</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Sorry, but I have to keep complaining about the documentation. Please</span><br><span>excuse the ranting.</span><br><span></span><br><span>Just one example from the manual:</span><br><span></span><br><span> ctest --build-options: Add extra options to the build step.</span><br><span> This option must be the last option with the exception of --test-command</span><br><span></span><br><span>End of available information.</span><br><span></span><br><span>I have not been able to figure out which CTEST_* variable these options</span><br><span>end up in, or how I could make them actually *affect* the build.</span><br><span></span><br><span>I am also still looking for a reference of variables used by CTest.</span><br><span></span><br><span>Quite obviously it is required to set both CTEST_SOURCE_DIRECTORY and</span><br><span>CTEST_BINARY_DIRECTORY in your script, as CTest keeps telling you if you</span><br><span>try to execute an empty script. I wonder if it wouldn't be easier if CTest</span><br><span>would assume the current directory as BINARY_DIR and the script directory</span><br><span>as SOURCE_DIR by default, but that might be just me.</span><br><span></span><br><span>That I have to set CTEST_COMMAND manually when I obviously just called the</span><br><span>executable, conveniently passing a working invocation in argv[0]). Strange.</span><br><span></span><br><span>CTEST_SITE / CTEST_BUILD_NAME constitute the identification sent to the</span><br><span>CDash server, as I found out perusing some example scripts on the Wiki,</span><br><span>none of which really explaining what is done. Nice, but why ain't I told</span><br><span>in plain English?</span><br><span></span><br><span>As SVN user, I have to set CTEST_CHECKOUT_COMMAND myself (to something</span><br><span>resembling "svn checkout ${MY_REPOSITORY} ${CTEST_SOURCE_DIRECTORY}".</span><br><span>Figured it out, works. But apparently CTEST_UPDATE_COMMAND is something</span><br><span>else entirely, as CTest insists on appending "update --non-interactive"</span><br><span>on its own accord...</span><br><span></span><br><span>It is possible to trial & error your way around all this, but I would</span><br><span>REALLY prefer to have a reference list, telling me which features I might</span><br><span>be missing, or how I should escape quotation marks and semicolons in a</span><br><span>-DCMAKE_PREFIX_PATH= statement. Or why a statement that works when given</span><br><span>as CTEST_CONFIGURE_COMMAND fails when passed in ctest_configure( OPTIONS ).</span><br><span></span><br><span>Hence, again my question: Is the man page and the half-dozen pages in the</span><br><span>Wiki really all there is in freely available documentation on CTest?</span><br><span></span><br><span>Regards,</span><br><span>-- </span><br><span>Martin Baute</span><br><span><a href="mailto:solar@rootdirectory.de">solar@rootdirectory.de</a></span><br><span></span><br><span>--</span><br><span></span><br><span>Powered by <a href="http://www.kitware.com">www.kitware.com</a></span><br><span></span><br><span>Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a></span><br><span></span><br><span>Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ">http://www.cmake.org/Wiki/CMake_FAQ</a></span><br><span></span><br><span>Follow this link to subscribe/unsubscribe:</span><br><span><a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a></span><br></div></blockquote></body></html>