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

[Hans-Peter Jansen]

On Wednesday 26 March 2003 14:59, Phil Thompson wrote:
>
> Sorry, I think you've misunderstood. The -r flag should define the full
> path of the Qt library directory - not just a component of it - like the -i
> flag for the header files. This is more flexible because it allows any
> arbitary directory to be specified.
>
> Same for -t - or does the -d flag already do it?
>
> Phil

I understood your concerns, but hesitated to make such deep changes.
Attached is what you asked for ;-) Hopefully all is well, especially the
win32 changes, which I haven't tested.

Here is something (hopefully) suitable for the ChangeLog:
Added -r flag to the build system to explicitly specify the Qt library 
directory. This is useful for 64 bit systems, where the libs are placed 
in $QTDIR/lib64, unlike the default $QTDIR/lib.
Same goes for the new -t flag, which specify the python base directory,
which is /usr/lib64/python#.# on such systems. This option takes 
priority over -d.
For concatenated builds (-c), a -j # flag was added to the build system 
for splitting huge modules, consisting of more then 100 single c++ modules, 
into # of pieces. This is useful in SMP environments, combined with 
make -j #, where # should correspond, to saturate the CPUs. It's also 
helpful for troubling c++ compilers and memory constraint systems, which 
may 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: 10523 bytes
Desc: not available
Url : http://www.riverbankcomputing.com/pipermail/pyqt/attachments/20030326/17131a41/PyQt-libopt-catsplit.bin