[CMake] CTEST_CHECKOUT_COMMAND vs. CTEST_UPDATE_COMMAND

Karthik Krishnan karthik.krishnan at kitware.com
Thu Jun 24 13:46:38 EDT 2010


On Thu, Jun 24, 2010 at 10:57 PM, Convey, Christian J CIV NUWC NWPT <
christian.convey at navy.mil> wrote:

> Thanks.  How does ctest know whether to employ "CVS_UPDATE_OPTIONS" vs.
> "SVN_UPDATE_OPTIONS" ?
>

Based on what CTEST_UPDATE_TYPE (CVS/SVN etc) is set to. If it isn't set, it
tries to determine one it by scanning the source directory to see if there
are CVS/, .svn/ directories, or fail with an error.

See Modules/CTest.cmake . The logic is all there...


>
> Also, the format you gave for "CVS_UPDATE_OPTIONS" looks like it has hte
> format of a line in the cache file.  Is there some reason I'd need to force
> it into the cache, or is it okay for me to achieve the same effect using a
> SET(CVS_UPDATE_OPTIONS ...) call?
>
> - Christian
>
> > -----Original Message-----
> > From: Karthik Krishnan [mailto:karthik.krishnan at kitware.com]
> > Sent: Thursday, June 24, 2010 11:51
> > To: Convey, Christian J CIV NUWC NWPT
> > Cc: cmake at cmake.org
> > Subject: Re: [CMake] CTEST_CHECKOUT_COMMAND vs. CTEST_UPDATE_COMMAND
> >
> > You can specify the update options.. for instance :
> >
> >   CVS_UPDATE_OPTIONS:STRING=-d -A -P
> >
> > similarly, there's
> >
> >   SVN_UPDATE_OPTIONS
>
> [snip]
>
> _______________________________________________
> 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/35802b26/attachment.htm>


More information about the CMake mailing list