Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Nigel Stewart
Here is what we're using as a non-Python alternative... sed "s/ \* Generated by SIP.*/ \*/" -i tmp/*.h tmp/*.cpp diff -ruN src tmp | patch -d src Sadly: sed, diff and patch on solaris are a little different, so this solution is not quite as portable as it needs to be... Nigel

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Nigel Stewart
Experimenting here with diff and patch... diff -ruN out tmp | patch -d out We don't have any Python dependency in our build toolchain. Maybe I'll just add another step to strip out the lines with timestamps... Here is what we're using as a non-Python alternative... (We use Cygwin

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Nigel Stewart
Experimenting here with diff and patch... diff -ruN out tmp | patch -d out However, there is one issue, perhaps SIP could provide an option _not_ to put timestamps in the wrapper code comments... :-) Why not use Gerard's script which handles this? We don't have any Python dependency in

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Giovanni Bajo
Phil Thompson <[EMAIL PROTECTED]> wrote: >> My experience is that GCC cannot handle PyQt3 single-file version and takes >> like 20 minutes to compile it, while I can compile PyQt3 single-file with >> MSVC in roughly 100 seconds. Are you saying that this scenario is going to >> change with PyQt4? >

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Jim Bublitz
On Tuesday 28 February 2006 09:18, Giovanni Bajo wrote: > Phil Thompson <[EMAIL PROTECTED]> wrote: > > With one source file (plus lots of header files) the whole of PyQt4 takes >> 2 minutes 50 seconds on my 2GHz Opteron. Microsoft compilers struggle with > > such large source files. > My experienc

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Yann Cointepas
But, only sip knows what files will be generated because it depends of the input sip file(s) content. Moreover, only sip knows the exact structure of the comments it adds at the begining of each file. This comments must not be taken into account when comparing files (it contains date). If the comme

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Andreas Pakulat
On 28.02.06 18:18:42, Giovanni Bajo wrote: > Phil Thompson <[EMAIL PROTECTED]> wrote: > > > With one source file (plus lots of header files) the whole of PyQt4 takes > 2 > > minutes 50 seconds on my 2GHz Opteron. Microsoft compilers struggle with > > such large source files. > > My experience is

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Phil Thompson
On Tuesday 28 February 2006 5:18 pm, Giovanni Bajo wrote: > Phil Thompson <[EMAIL PROTECTED]> wrote: > > With one source file (plus lots of header files) the whole of PyQt4 takes > > 2 > > > minutes 50 seconds on my 2GHz Opteron. Microsoft compilers struggle with > > such large source files. > > My

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Phil Thompson
On Tuesday 28 February 2006 5:25 pm, Nigel Stewart wrote: > > 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, > > Experimenting here with di

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Nigel Stewart
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, Experimenting here with diff and patch... diff -ruN out tmp | patch -d out However, there is one i

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Giovanni Bajo
Phil Thompson <[EMAIL PROTECTED]> wrote: > With one source file (plus lots of header files) the whole of PyQt4 takes 2 > minutes 50 seconds on my 2GHz Opteron. Microsoft compilers struggle with > such large source files. My experience is that GCC cannot handle PyQt3 single-file version and takes

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Phil Thompson
On Tuesday 28 February 2006 4:30 pm, Giovanni Bajo wrote: > Nigel Stewart <[EMAIL PROTECTED]> wrote: > >> What does this have to do with SIP again? I don't remember GCC not > >> generating the object files if the source code is not changed. > > > > A compiler takes one input file and creates o

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Nigel Stewart
>> uic and moc avoid touching files unnecessarily, and so could SIP. I wasn't aware of uic and mock behaving like that. True, it's qmake that is uic and moc dependency aware... A wrapper that generated the .sip files into a temporary directory, compared them against previously generated fi

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Gerard Vermeulen
On Tue, 28 Feb 2006 10:18:31 -0600 Nigel Stewart <[EMAIL PROTECTED]> wrote: > > >> It could be argued that SIP is part of a broader toolchain > > > > What does this have to do with SIP again? I don't remember GCC not > > generating the object files if the source code is not changed. > > A

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Giovanni Bajo
Nigel Stewart <[EMAIL PROTECTED]> wrote: >> What does this have to do with SIP again? I don't remember GCC not >> generating the object files if the source code is not changed. > > A compiler takes one input file and creates one output file. Actually not really, since the input can also cont

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Phil Thompson
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 S

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Nigel Stewart
It could be argued that SIP is part of a broader toolchain What does this have to do with SIP again? I don't remember GCC not generating the object files if the source code is not changed. A compiler takes one input file and creates one output file. The granularity of SIP is differe

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Giovanni Bajo
Nigel Stewart <[EMAIL PROTECTED]> 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 bro

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Nigel Stewart
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 w

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Phil Thompson
On Tuesday 28 February 2006 3:10 pm, Yann Cointepas wrote: > Hi, > > What is the procedure to propose modification to sip ? You've just followed it. :) > I need a feature > that I am ready to program. I would like sip to have an option to generate > a C++ file only if it does not exists or if it

Re: [PyKDE] How to contribute to sip ?

2006-02-28 Thread Nigel Stewart
> I would like sip to have an option to generate a C++ file only if it does not exists or if it is different from the existing one. This would greatly improve compilation time ... That would be very good indeed. Does it need to be optional? We would see some immediate benefits to

[PyKDE] How to contribute to sip ?

2006-02-28 Thread Yann Cointepas
Hi, What is the procedure to propose modification to sip ? I need a feature that I am ready to program. I would like sip to have an option to generate a C++ file only if it does not exists or if it is different from the existing one. This would greatly improve compilation time (using make dependen