On Wed, Jul 29, 2009 at 5:14 AM, Vladimir Prus<vladimir@codesourcery.com> wrote:
I personally find that putting configuration details into a file is superior approach compared to zillion of options or environment variables. Say, if you build a project with automake with zillion of configure options, those options are put directly in Makefile, in your build dir, so if you remove your build tree, you have to re-figure those options next time you build.
In fact, this is a flaw shared by CMake -- if you configure some project as:
cmake -Dfoo=blah -DBOOST_ROOT=whatever ../src
it helpfully puts those options into the cache file. Unfortunately, when the configure magic confuses itself (which does happen), your only solution is to remove the cache, and then you need to recall and pass the same options again.
FWIW, CMake has an option to provide an initial cache file (using -C cache-filename). So, you can place those configuration details into your own initial cache file, and ask CMake to start with that configuration (configuring whatever else it needs) if you need to re-configure your tree. - Doug