CMakeCache.txt

[William A. Hoffman]

At 05:53 AM 3/27/2006, David Faure wrote:
>autoconf used to always generate and reuse a config.cache, and then they changed the default
>so that the user had to specify --cache explicitely instead, presumably because many people
>didn't find out that they had to remove their config.cache after installing a library or changing
>whatever else on their system.
>
>cmake seems to have the same problem; people don't find out about the need to
>remove CMakeCache.txt if wrong things were detected. But I see how cmake needs
>to always use a cache, since any change to a CMakeLists.txt triggers a re-configuration....
>
>Suggestions/requests:
>a) not writing out CMakeCache.txt until the configuration step succeeds (so that at least
>during the initial attempt at configuring there is no need to remove it all the time).

If there is a fatal error during the configure step, cmake no longer saves out the
CMakeCache.txt file to address this problem. 

-Bill