[PyKDE] What am I missing?

[Phil Thompson]

Donald Beaudry wrote:
> 
> Phil Thompson <phil at river-bank.demon.co.uk> wrote,
> > I need more information about you particular problem with Qt.
> 
> Ok, here the build output:
> 
> $ make
> make  all-recursive
> make[1]: Entering directory `/home/donb/pykde/PyQt-2.0'
> Making all in qt
> make[2]: Entering directory `/home/donb/pykde/PyQt-2.0/qt'
> /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I..  -I/usr/local/include/python1.5 -I/usr/local/include/sip -I/usr/lib/qt-2.1.0/include  -I/usr/X11R6/include  -fno-exceptions -O2 -c qtcmodule.cpp
> c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/python1.5 -I/usr/local/include/sip -I/usr/lib/qt-2.1.0/include -I/usr/X11R6/include -fno-exceptions -O2 -Wp,-MD,.deps/qtcmodule.pp -c  -fPIC -DPIC qtcmodule.cpp -o qtcmodule.lo
> qtcmodule.cpp: In function `struct PyObject * registerClasses(struct PyObject *, struct PyObject *)':
> qtcmodule.cpp:10139: `Set_GBK' is not a member of type `QFont'

It looks like some extra functionality was introduced between Qt 2.1.0
and 2.1.1 when I had thought it was introduced between 2.0.2 and 2.1.0.
I don't keep every version of Qt around to do regression testing - I
keep the latest of each "strand", ie 1.44, 2.0.2, 2.1.1 and assume that
there are only bug fixes between version a.b.c and a.b.c+1 - so much for
assumptions.

As Qt 2.1.0 is fairly old I don't plan on fixing the problem. The
solution is to either upgrade or downgrade. Qt 2.2.0 has so many extra
goodies that people should upgrade if at all possible. The problem
shouldn't happen again because it's now much easier for me to respond to
new Qt releases so each one will get tested.

On a related note, Trolltech pulled a similar trick between the last
beta of 2.2.0 and the final 2.2.0. PyQt will not build under a 2.2.0
beta.

Phil