I ran into some odd CMake behaviour using both Borland Developer Studio 2006 on WinXP and Borland C++ Builder 6 on Win 2k. In both cases I was building KWWidgets (cvs) against a shared build of VTK (cvs) using latest CMake cvs. Cmake stops after notification of the VTK_DIR cache entry as it should but there is NO CMakeCache.txt file in the build dir!
-- Check for working C compiler: bcc32 -- Check for working C compiler: bcc32 -- works -- Check size of void* -- Check size of void* - done -- Check for working CXX compiler: bcc32 -- Check for working CXX compiler: bcc32 -- works -- Configuring done VTK not found. Set the VTK_DIR cmake cache entry to the directory containing VTKConfig.cmake etc. etc. Here are the contents of the KWWidgets build dir: .: CMakeFiles CMakeTestGNU.obj CMakeTestGNU.tds ./CMakeFiles: CMakeCCompiler.cmake CMakeCXXCompiler.cmake CMakeOutput.log CMakeSystem.cmake CMakeTmp ./CMakeFiles/CMakeTmp: CMakeFiles ./CMakeFiles/CMakeTmp/CMakeFiles: cmTryCompileExec.dir ./CMakeFiles/CMakeTmp/CMakeFiles/cmTryCompileExec.dir: This does NOT occur with CMake 2.0.6 and 2.2.3. My workaround is to just add a CMakeCache.txt with one cache entry for VTK_DIR. Dean _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
