[CMake] ctest meant to be re-entrant?

Convey, Christian J CIV NUWC NWPT christian.convey at navy.mil
Mon Jun 21 13:18:27 EDT 2010


Sorry, that was embarrassing.  Pretend I had said, "CTestTestFile.cmake" instead of "CTestConfig.cmake".

> CTestConfig.cmake should be a source file in your source 
> tree. Nothing should be writing it automatically.
> 
> 
> 
> On Mon, Jun 21, 2010 at 11:21 AM, Convey, Christian J CIV 
> NUWC NWPT <christian.convey at navy.mil> wrote:
> 
> 
> 	I'm having trouble getting my mind around how CTest is 
> intended to be used.  Could someone explain this to me?
> 	
> 	When you embed ctest-related statements into a 
> CMakeLists.txt file, and then run cmake on that file, you 
> produce a "CTestConfig.cmake" file.  This file is eventually 
> executed by "ctest".
> 	
> 	But ctest also has the ability to run "cmake".  In the 
> worst-case (in my mind) scenario, this ultimately leads to 
> "ctest" causing the rewriting of the very "CTestConfig.cmake" 
> file that it's presently executing.
> 	
> 	Is this intended?  Or does it lie outside of the 
> intended ways of using ctest?
> 	
> 	
> 	_______________________________________________
> 	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 --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5218 bytes
Desc: not available
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100621/a9ad8ad9/attachment.bin>


More information about the CMake mailing list