[PyKDE] pyuic

[Phil Thompson]

Jonathan Gardner wrote:
> 
> On Saturday 07 July 2001 14:54, Boudewijn Rempt wrote:
> > On Sat, 7 Jul 2001, Jonathan Gardner wrote:
> > > I'm running SuSE 7.1 on an i386. I installed all the default rpm's (PyQt
> > > and sip, they're both version 2.2). Everything works great, except there
> > > is a bug in pyuic where it fails to insert a "self." every once in a
> > > while. I am pretty sure a bug like this would've been caught between
> > > version 2.2 and 2.4.
> > >
> > > So I went to download 2.4, and I can't get the thing to compile. I've
> > > tried it with the default qt library, with qt 2.2.3 library and I've
> > > tried a lot of different combinations. Do I need qt 2.3.1 in order to get
> > > it all to compile?
> >
> > I use SuSE 7.1 myself, and was forced to compile PyQt on a clean system
> > yesterday myself, and I didnt't have a problem - but I must say that I
> > did install Python 2.1 in /usr/local myself. Have you compiled & installed
> > sip succesfully? You cannot use PyQt 2.4 with sip 2.2. Can you give us
> > a bit more of what goes wrong on compilation?
> 
> Okay, this is what I did this time, just to make sure it wasn't an older
> version of Qt causing any problems.
> 
> I downloaded qt-2.3.1 and installed it at /usr/lib/qt-2.3.1
> I am pretty sure it is working because I was able to use the new designer,
> and it said "Qt v.2.3.1" in the help box.
> 
> Next, I removed "sip" and "PyQt" rpms by doing:
> 
> rpm -e PyQt
> rpm -e sip
> 
> Then I went into the old directory where I untarred sip-2.4 and tried to
> build it before. I entered the following commands:

Safer to delete the directory and untar the sources again.

> ./configure --with-qt-dir=/usr/lib/qt-2.3.1 --prefix=/usr
> make clean
> make
> make check
> make install
> 
> It was quite disconcerting that "make check" did nothing, but otherwise,
> there were no errors.
> 
> Then I went into the old directory where I untarred PyQt-2.4 and tried to
> build it before. I entered the following commands:

Ditto.

> ./configure --with-qt-dir=/usr/lib/qt-2.3.1 --prefix=/usr  \
> --with-sip-libraries=/usr/lib --with-sip-includes=/usr/include/sip
> make clean
> make
> 
> On make, I got the following error:
> 
> c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/python2.0 -I/usr/include/sip
> -I/usr/lib/qt-2.3.1/include -I/usr/X11R6/include -fno-exceptions -O2 -c
> qtcmodule.cpp      -fPIC -DPIC -o qtcmodule.lo
> In file included from qtcmodule.cpp:4099:
> sipqtProxyqt.moc:45: new declaration `static void
> sipProxyqt::staticMetaObject()'
> sipqtProxyqt.h:36: ambiguates old declaration `static class QMetaObject *
> sipProxyqt::staticMetaObject()'
> sipqtProxyqt.moc: In function `void
> __static_initialization_and_destruction_0(int, int)':
> sipqtProxyqt.moc:29: no matching function for call to
> `QMetaObjectInit::QMetaObjectInit (QMetaObject * (*)())'
> /usr/lib/qt-2.3.1/include/qmetaobject.h:259: candidates are:
> QMetaObjectInit::QMetaObjectInit(void (*)())
> /usr/lib/qt-2.3.1/include/qmetaobject.h:261:
> QMetaObjectInit::QMetaObjectInit(const QMetaObjectInit &)
> make[2]: *** [qtcmodule.lo] Error 1
> make[2]: Leaving directory `/root/downloads/PyQt-2.4/qt'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/root/downloads/PyQt-2.4'
> make: *** [all-redirect] Error 2

Errors around meta objects are often related to having code lying around
generated from an older version of moc.

Phil