[PyKDE] [PATCH] new build.py options for lib64 and cat split

Hans-Peter Jansen hpj at urpla.net
Wed Mar 26 14:28:00 GMT 2003


Hi Phil,

next attempt for $subject. They're all separate lowercase options now.
Let me know, if this is acceptable for you. I've thought some time on 
how to make the path handling simpler without loosing flexibility nor 
functionality, but don't wanted to risk breaking stuff in obscure 
environments, which I cannot test here. I think, that stability has 
higher priority by now shortly before the 3.6 release. This approach 
has the advantange to be easily adopted by current build systems, too.

One possible alternative would be changing -d to specify a relative
dir, e.g. "site-packages", and let the new -t option specify the python 
base, but this leads to the afore mentioned disadvantage.

The lib64 stuff is logically chacked against 64 bit package listings
from SuSE.

Here is something (hopefully) suitable for your ChangeLog:
Added -r flag to the build system to specify the Qt library directory.
This is useful for 64 bit systems, where the libs are placed in a "lib64" 
directory. Same goes for the new -t flag, which specify the python lib 
directory. Both options defaults to "lib" in order to keep the current 
behaviour, and should be specified as "lib64" on such systems.
Added -j # flag to the build system for splitting huge modules, consisting 
of more then 100 single c++ modules, into # of pieces, when concatenated (-c).
This is useful in SMP environments, combined with make -j #, where # should 
correspond. It's also useful for troubling c++ compilers, which fail on such 
big sources otherwise.

Pete
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PyQt-libopt-catsplit.diff
Type: text/x-diff
Size: 9095 bytes
Desc: not available
Url : http://www.riverbankcomputing.com/pipermail/pyqt/attachments/20030326/2cbe4433/PyQt-libopt-catsplit.bin


More information about the PyQt mailing list