Hi again, > From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On > Behalf Of Jan Wurster > Sent: Freitag, 20. November 2009 16:49 > To: cmake@cmake.org > Subject: [CMake] CTEST_UPDATE command and deep file hierarchies in > repository
> I've had a look at the relevant ctest-code sections and it seems that > currently CTEST_UPDATE_COMMAND will be used from within > CTEST_SOURCE_DIRECTORY, i.e. using relative paths. Is there a way to > change this behaviour to using the absolute path > (CTEST_SOURCE_DIRECTORY should contain this) like it is used with CTEST_EXTRA_UPDATES (that still seem to rely von CTEST_CVS_COMMAND, but can be abused to work in that case)? Yep - apparently there is ;) I just found a way to do this in case other people are interested: CTEST_SVN_UPDATE_OPTIONS is interpreted in a way that one could put the actual full path in front of any arguments one might or might not require. That way the generated command line is as required and the update works as intended. Nevertheless - would using the update options parameter be the way to do this or would rather the basic behaviour be changed in a future version? Cheers and best regards, -.jan.- _______________________________________________ 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
