On Tuesday 28 February 2006 3:50 pm, Nigel Stewart 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.
I wasn't aware of uic and mock behaving like that. If so it's a dumb thing to do. > 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... Agreed - but there is a right place to fix things, and this isn't it. A wrapper that generated the .sip files into a temporary directory, compared them against previously generated files and replaced them if they were different isn't very difficult to write. Phil _______________________________________________ PyKDE mailing list [email protected] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
