[CMake] CTEST_CHECKOUT_COMMAND vs. CTEST_UPDATE_COMMAND

Convey, Christian J CIV NUWC NWPT christian.convey at navy.mil
Thu Jun 24 10:27:45 EDT 2010


Could someone explain something to me about CTest's conventions?

I'm reading throught this page:
http://www.cmake.org/Wiki/CTest:Using_CTEST_and_CDASH_without_CMAKE

It sounds like the variable "CTEST_CHECKOUT_COMMAND" is meant to contain the ensure checkout command, including all arguments.

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.

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?

Thanks,
Chritian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5218 bytes
Desc: not available
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100624/4d46c2f0/attachment.bin>


More information about the CMake mailing list