From kde-buildsystem  Mon Oct 24 08:00:18 2005
From: coolo () kde ! org (Stephan Kulow)
Date: Mon, 24 Oct 2005 08:00:18 +0000
To: kde-buildsystem
Subject: very basic SConfigure support available
Message-Id: <200510241000.20100.coolo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-buildsystem&m=113280651211845

Am Montag, 24. Oktober 2005 04:50 schrieb Michael Olbrich:
> On Sun, Oct 23, 2005 at 06:19:16PM +0200, David Faure wrote:
> > I agree for the big checks like fam, bzip2 etc.
> >
> > But let's not mix the topics :)
> > I don't want to have to write one object per system header file that
> > kdecore needs, to then write obj.Requires("sys_param_h") where
> > sys_param_h is its own python object.
> >
> > I like very much the API suggested by Stephan :)
>
> I agree. I have to admit I wasn't really thinking about system headers
> and things like that at the time.
> I have one other question though: What happens when a header test fails?
> Currently configure will fail completely. That's ok for kdelibs. But I
> had the problem once that a missing header caused configure in an extragear
> module to fail.
> As the tests are now specified where they are needed it should be
> possible to disable the affected directory and everything depending on
> it. A warning is a prominent place would probably be a good idea.
>
There are really little headers we fail on. And extragear is actually not to 
fail at all unless qt or kde is not found.

Greetings, Stephan