[Cmake] Quick configuration
William A. Hoffman
billlist at nycap . rr . com
Fri, 05 Dec 2003 12:29:27 -0500
CMake has always supported out-of-source builds.
The command line was changed so that you have to specify
the binary directory.
In the past:
cmake -> no arguments would do and in-source build tree
Now you have to do this:
cmake . -> you must specify the build directory
cmake is for non-interactive builds.
ccmake is always interactive.
cmake . -> builds in source
ccmake . -> builds in source
You should not have to run cmake first.
ccmake . will build for the CMakeLists.txt files
in the current directory.
-Bill
At 03:54 AM 12/5/2003, David Svoboda wrote:
>Short time ago a updated CMake. Previously I use v1.6.7, now I'm using
>1.8.x
>Previously, 'cmake' or 'ccmake' had to be executed in the directory,
>where the 'CMakeLists.txt' file was stored. Now, thanks to the possibility
>of out-of-source compilation,, another way is used -> 'cmake' or 'ccmake'
>is exectuted for an arbitrary directory with one argument, which is the
>directory, where the appropriate 'CMakeLists.txt' files is stored.
>
>And now the question - why cannot I type 'ccmake .' immediately? - it does
>not work properly. When I configure my Makefiles with Cmake, I must follow
>these steps:
>1. cmake . -> this tries to configure without my interaction
>2. ccmake .. -> now I can do this (but as the second step only) and
>configure required values (directories, files, etc.)
>
>
>David
>_______________________________________________
>Cmake mailing list
>Cmake at www . cmake . org
>http://www . cmake . org/mailman/listinfo/cmake