On Friday 14 November 2008, Bill Hoffman wrote: > Alexander Neundorf wrote: ... > > So the user would just tell ctest_configure() which variables to hand > > over to cmake, and ctest_configure() would then write the CMakeCache.txt > > (or a cmake script to be preloaded using -C). > > Or we could stick with the current file(WRITE CMakeCache.txt) approach...
This feels quite out of place IMO. There are the high-level ctest_foo() commands, which care about creating the directories, doing cvs/svn update and so on, and in the middle of that I should write in a file which name I then have to hardcode and where I have to know the format of CMakeCache.txt, which is otherwise treated as internal implementation detail. I'll send another patch in a few days. Alex _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
