<br><br><div class="gmail_quote">On Thu, Jun 24, 2010 at 10:27 AM, Convey, Christian J CIV NUWC NWPT <span dir="ltr"><<a href="mailto:christian.convey@navy.mil">christian.convey@navy.mil</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Could someone explain something to me about CTest's conventions?<br>
<br>
I'm reading throught this page:<br>
<a href="http://www.cmake.org/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE" target="_blank">http://www.cmake.org/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE</a><br>
<br>
It sounds like the variable "CTEST_CHECKOUT_COMMAND" is meant to contain the ensure checkout command, including all arguments.<br>
<br>
However, the "CTEST_UPDATE_COMMAND" is simply set to (for example) "svn". So if ctest is going to use this variable, it must be planning on supplying its own command-line arguments, such as "update" and (optionally) the path of the source code to be updated.<br>
<br>
So here's my question: Is there supposed to be a naming convention in CTest such that "..._COMMAND" is a complete command with all arguments? Or the basic program name without any arguments? Or is this just something for which no pattern exists?<br>
</blockquote><div><br><br>It would be nice if there were a rock solid naming convention behind this... most _COMMAND variables are in fact complete command lines. But CTEST_UPDATE_COMMAND is an exception to that convention. I would have to dig through the rest to know for sure, but I think there are probably other exceptions as well...<br>
<br>Bottom line:<br>Don't rely on conventions being followed absolutely. Read the documentation and even the source code when in doubt.<br><br>Looking at real world example scripts on the public dashboards is always a good idea, too. For example: <a href="http://www.cdash.org/CDash/viewNotes.php?buildid=645854">http://www.cdash.org/CDash/viewNotes.php?buildid=645854</a> (click on the little note/document icon on a build row to see attached notes, by *convention* this is the ctest -S script used to submit CMake dashboards.....) :-)<br>
<br><br>HTH,<br>David<br><br><br><br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Thanks,<br>
Chritian<br>
<br>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br>