[CMake] CTEST_CHECKOUT_COMMAND vs. CTEST_UPDATE_COMMAND
David Cole
david.cole at kitware.com
Thu Jun 24 11:58:01 EDT 2010
On Thu, Jun 24, 2010 at 10:27 AM, Convey, Christian J CIV NUWC NWPT <
christian.convey at navy.mil> wrote:
> 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?
>
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...
Bottom line:
Don't rely on conventions being followed absolutely. Read the documentation
and even the source code when in doubt.
Looking at real world example scripts on the public dashboards is always a
good idea, too. For example:
http://www.cdash.org/CDash/viewNotes.php?buildid=645854 (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.....) :-)
HTH,
David
>
> Thanks,
> Chritian
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100624/eb9ee7b1/attachment.htm>
More information about the CMake
mailing list