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

List:       pykde
Subject:    Re: [PyQt] Pyqt development rebuilds?
From:       Gerard Vermeulen <gerard.vermeulen () grenoble ! cnrs ! fr>
Date:       2007-07-25 20:09:05
Message-ID: 20070725220905.3556b991 () zombie ! grenoble ! cnrs ! fr
[Download RAW message or body]

On Wed, 25 Jul 2007 12:03:00 -0700
Peter Shinners <peters@imageworks.com> wrote:

> I have a copy of the Pyqt code. It is easy to build, but I cannot
> figure how to do an incremental rebuild after changing one file?
> 
> The configure.py removes all the created .h and .cpp files. But
> touching the original .sip files does not trigger a rebuild.
> 
PyQwt's configure.py puts all .h and .cpp file in a temporary
directory and copies them only to the build directory when
the generated files differ significantly. You have to skip
the timestamps -- see lazy_copy_file() in configure/configure.py:
http://pyqwt.cvs.sourceforge.net/pyqwt/pyqwt5/configure/configure.py?revision=1.22&view=markup

If you consider this to much work then I suggest (in decreasing ratio
of ease of setup to decrease in build time):
- ccache (ccache.samba.org) can speed up compilation by a factor 10.
- play with the configure.py's and make's -j option if you have
  a multicore machine (compiling is very CPU intensive, so using
  two cores instead of one gives you almost a factor 2).
- distcc (distcc.samba.org) is also impressive, but is not as
  easy to set up as ccache (you can combine distcc with ccache).

Gerard

_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]