[PyKDE] PyKDE-3.7-4 Release

Gordon Tyler gordon at doxxx.net
Fri Aug 15 23:43:01 BST 2003

On August 15, 2003 04:07 pm, you wrote:
> No - it's a feature :)

Hmmm.... ;)

> > python 2.2 installed into /usr (deb package), sip 3.7 and pyqt
> > 3.7 installed into /usr/local.
> build.py wasn't written to allow for that possibility, but maybe
> should be (somewhat)

The reason I do this is to make it easier to separate files installed by 
Debian packages and files installed by custom-compiled source packages.

> I'd go as far as searching sys.path for libqtcmodule.so - it
> appears that would succeed in your case. Beyond that, it
> complicates the build.py code too much in my opinion, and worse,
> makes it much harder to troubleshoot install problems (newbies).
> That would allow ldd to work and also allow the correct -L args
> to be passed to the make files.

I agree that searching sys.path would solve the problem. I assume by 
"complicates the build.py code too much" you're referring to the additional 
option for the location of PyQt modules? I don't see how.

> Would that work in your situation? Where do you have libsip
> installed?

I think so. libsip is in the same directory. I install everything into 

These are the build.py commands I use:

sip: python2.2 build.py -b /usr/local/bin -d 
/usr/local/lib/python2.2/site-packages -e /usr/local/include/python2.2 
-fno-exceptions -l qt-mt -u
pyqt: python2.2 build.py -b /usr/local/bin -c -d 
/usr/local/lib/python2.2/site-packages -e /usr/local/include/python2.2 
-fno-exceptions -l qt-mt -n /usr/local/include -o /usr/local/lib -s 
/usr/local/lib/python2.2/site-packages -u
pykde: python2.2 build.py -d /usr/local/lib/python2.2/site-packages -e 
/usr/local/include/python2.2 -k /usr -s 
/usr/local/lib/python2.2/site-packages -v 

BTW, on a related note, are you still going to apply my patch 
'PyKDE-3.5-2_subclass.patch' or some form of it? I had to apply it myself now 
to make my application work.


More information about the PyQt mailing list