[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-buildsystem
Subject:    very basic SConfigure support available
From:       michael-olbrich () web ! de (Michael Olbrich)
Date:       2005-10-24 2:50:15
Message-ID: 20051024025015.GC24141 () a168 ! apm ! etc ! tu-bs ! de
[Download RAW message or body]

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.

michael


[prev in list] [next in list] [prev in thread] [next in thread]