[PyKDE] How to contribute to sip ?

[Giovanni Bajo]

Nigel Stewart <ns at fluent.com> wrote:

>> I wouldn't accept this change as it doesn't really have anything to do
with
>> what SIP does (although I readily admit that some of SIP's existing
>> functionality also falls into that category).
>
> Phil,
>
> It could be argued that SIP is part of a broader toolchain (in our case,
> gmake and qmake) that would benefit from SIP taking some care not to
> touch unchanged files.  uic and moc avoid touching files unnecessarily,
> and so could SIP.
>
> Currently, our sip-based python bindings are the bottleneck in our
> incremental builds.  We bypass this as much as possible, (cheating the
> dependencies) but we shouldn't need to be doing that kind of workaround...


What does this have to do with SIP again? I don't remember GCC not
generating the object files if they source code is not changed. It's up to
the build process to detect if the source file is changed and call the
compiler (SIP, uic, gcc, ecc.) if necessary. Usually, that is done by
checking the date of the last modification. More complex build system like
scons use intelligent MD5 signatures (which ignore comments in source files
and whatnot).

So, why can't you configure your build system so that it doesn't call SIP in
the first place if the header file has not changed?
-- 
Giovanni Bajo