Boost Interest :
From: Doug Gregor (doug.gregor_at_[hidden])
Date: 2008-05-27 13:11:34
On Tue, May 27, 2008 at 10:51 AM, David Abrahams <dave_at_[hidden]> wrote:
> on Tue May 27 2008, "Doug Gregor" <doug.gregor-AT-gmail.com> wrote:
>> It won't require any hand-configuration. There is an easy way to
>> automate the configuration process by giving CMake a pre-populated
>> list of cache entries that drive the configuration.
> Can you explain what you mean by "cache entries?"
Sure. A build directory for a CMake project contains lots of
information about the built: makefiles or project files, the actual
object files, libraries, and executables that have been built, and
CMake configuration information for that build tree. The CMake
configuration information is stored in the file CMakeCache.txt, which
has a set of name-value pairs in it called "cache entries". When you
run CMake on a build tree, CMake will read in these cache values,
which can be modified or updated by the CMake build scripts
(CMakeLists.txt files, and whatever they include). So, to automate
configuration for testing, one would set the cache entry
Each of the cache entries will show up in the CMake GUI or the Curses
interface, so they can be edited. Then one re-runs CMake to update the
configuration. CMakeCache.txt is also hand-editable.