On Tue, 26 Jan 2010 14:38:59 +0100, Lorenzo Masini <[email protected]> wrote: > Hi list! > > I'd like to submit you the patch attached. > It is a sip patch that adds a -D switch which prints the dependency tree > of a sip file on stdout. > > I've patched the sipdistutils too, adding the capability of discover the > changes into a sip file included by the ones we are building.
I've been thinking about this as well - but I don't like this particular implementation as it is too inflexible. I want to decouple SIP and its build system (and possibly remove the latter in SIP5). SIP should just provide metadata (file names, dependencies etc) about the code it has generated. Different build systems can use the metadata as they need to. The question is what format the metadata should be in? I'm inclined to stealing Mercurial's concept of templates - which is effectively simple macro expansion - rather than imposing a fixed format that a build system would then have to parse. Suggestions welcome. Phil _______________________________________________ PyQt mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/pyqt
