Thanks. How does ctest know whether to employ "CVS_UPDATE_OPTIONS" vs. "SVN_UPDATE_OPTIONS" ?
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.krish...@kitware.com] > Sent: Thursday, June 24, 2010 11:51 > To: Convey, Christian J CIV NUWC NWPT > Cc: cmake@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]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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
