KDE/kdelibs/cmake/modules
David Faure
faure at kde.org
Tue Apr 18 17:38:17 CEST 2006
On Tue, Apr 18, 2006 at 07:22:17AM -0500, Matt Rogers wrote:
> On Tuesday 18 April 2006 06:22, David Faure wrote:
> > SVN commit 531000 by dfaure:
> >
> > More use of the cache; fixing previous commit to not recheck everytime when
> > something isn't available (e.g. agg for me).
>
> is there a way we can make it check if we've installed something that wasn't
> available before?
Hmm, but that's the point, I don't want it to work that way.
When you install something that wasn't available before, you have to remove CMakeCache.txt,
this is just like with autoconf and config.cache [except that they made the config.cache
feature disabled by default at some point]. But we can't disable it with cmake since
any change in e.g. the list of source files triggers a re-configuration, which is more often
than with autoconf.
The point is that 99% of the time, when the configuration code is re-evaluated, it's because
some CMakeLists.txt has changed, and there's no point in making that slow by running all sorts
of pkgconfig commands etc. just to check if something new got installed. That's the case that
should be as fast as possible.
In the 1% case of something has been installed, rm CMakeCache.txt.
--
David Faure
faure at kde.org
More information about the Kde-buildsystem
mailing list