Do *not* distribute CMakeCache.txt. It simply will not work. CMake must be run against CMakeLists.txt to produce CMakeCache.txt (and all the rest of the initial binary tree) on each target build machine...
On 6/8/07, abhijeet mhatre <[EMAIL PROTECTED]> wrote:
> Hi > I configure cmake by writing a CMakeLists.txt file in a source folder. > It runs fine. > > Now if I move the folder to some other location, cmake complains that the > files still refer to the previous location. Then I have to edit > CMakeCache.txt and replace the project path at 3-4 there. Then it works > fine. > > Is there any elegant way to do this. >>Do out-of-source builds. When you want the output to appear somewhere >>else, nuke the output directory and start over. >>http://www.cmake.org/Wiki/CMake_FAQ <http://www.cmake.org/Wiki/CMake_FAQ> You cannot simply move CMake >>output directories around in the filesystem. They use hardcoded >>absolute paths for safety, so if you want them somewhere else you must >>regenerate them. Suppose if I want distribute my project with the source code, CMake files and all, how do I do this? I dont mind regenerating build files using "cmake ." but I dont want to edit the CMakeLists.txt and CMakeCache.txt when I distriubute my project. Is this doable? regards Abhijeet ------------------------------ Get the free Yahoo! toolbar<http://us.rd.yahoo.com/evt=48226/*http://new.toolbar.yahoo.com/toolbar/features/norton/index.php>and rest assured with the added security of spyware protection. _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
_______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
