KDE/kdelibs/cmake/modules

David Faure faure at kde.org
Wed Apr 19 11:30:25 CEST 2006


On Tue, Apr 18, 2006 at 10:40:24PM +0200, Alexander Neundorf wrote:
> On Tuesday 18 April 2006 22:31, you wrote:
> > On Tue, Apr 18, 2006 at 09:59:13PM +0200, Alexander Neundorf wrote:
> ...
> > So I'm OK with reverting CACHED_FOO when the test is only about using
> > FIND_XXX, but I think my changes still make sense for many checks.
> >
> > Or should PKGCONFIG() itself use the cache more aggressively ?
> 
> Probably. I also already thought about this some time ago, but didn't get 
> around to do something.

In fact I don't think we should do it that way. We should still call the macro
5 times, and we would have to remember what pkg-config issued the first time,
in order to then run the regex-replace commands again....

Executing command /usr/bin/pkg-config fontconfig --exists
Executing command /usr/bin/pkg-config fontconfig --variable=includedir
Executing command /usr/bin/pkg-config fontconfig --variable=libdir
Executing command /usr/bin/pkg-config fontconfig --libs
Executing command /usr/bin/pkg-config fontconfig --cflags
-- Found FONTCONFIG: /usr/lib/libfontconfig.so

Better use the cache on the final results rather than the stuff pkg-config
issued to us, IMHO.

--
David Faure
faure at kde.org



More information about the Kde-buildsystem mailing list