Yes. that is the preferred way to use CMake. One configuration per
build directory. You can rebuild which ever one you want.
Having said that boost's cmake files have managed to allow all the
configurations in one directory.
Mike
On Nov 26, 2008, at 12:02 PM, Steven Van Ingelgem wrote:
Hi Eric,
That's pretty bad as well, because if I change 1 small cpp file, I
will be rebuilding everything... Not very nice :).
I always run "cmake .", but is it possible to do for example:
------
mkdir static_release
cd static_release
cmake ..
------
Thanks,
Steven
2008/11/26 Eric Noulard <[EMAIL PROTECTED]>
2008/11/26 Steven Van Ingelgem <[EMAIL PROTECTED]>:
> What I would like to do is create some kind of batch generation
for every
> combination of debug/release, static/dynamic.
>
> So I would call:
> echo building static release
> cmake -D cfg=release -D link=static .
> make all && make install
>
> echo building dynamic release
> cmake -D cfg=release -D link=dynamic .
> make all && make install
if you want to batch all those builds then may be you should
always start from a pristine empty build dir, thus you won't have to
bother on pre-existing cache since there won't be any.
echo building static release
rm -rf release_static
mkdir release_static
cd release_static
cmake -D cfg=release -D link=static .
make all && make install
cd ..
echo building dynamic release
rm -rf release_dynamic
mkdir release_dynamic
cd release_dynamic
cmake -D cfg=release -D link=dynamic .
make all && make install
cd ..
etc...
--
Erk
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
