[PyQt] Cross Compiled PYQT
hglenn at 2g-eng.com
Fri Apr 18 20:18:26 BST 2008
Thanks for the Reply David,
Yep, we had tested it with a few of our simple apps that we had been
writing on the PC before that, and the error was the same. So we went
straight to the shell and started typing to see where the problem started.
Thanks for the reply, and thanks for posting your original work on the
web. Without it we would be a lot farther off in trying to get this working.
David Boddie wrote:
> On Sat, 12 Apr 2008 10:13:03 +0200, Aaron Digulla wrote:
>> Hal Glenn schrieb:
>>> OK, I ended up following David's example completely, at first we had
>>> tried with newer versions of Python QT sip etc but each one possessed a
>>> problem so we dropped back to using David's work almost word for word,
>>> accept in order to cross compile Python we had to edit it's Makefile
>>> slightly to build the correct architecture python libs.
> The patches need to be updated to the latest versions - not something I
> have time for right now, unfortunately. :-(
>>> One we had all
>>> that done, we copied the tree over to our device (gumstix) and ran a few
>>> tests on QT and Python. Both seemed to be working fine.
>>> But once we started trying to looking PYQT we got a Seg fault... don't
>>> suppose any of you know what this means? besides it's broke :)
>>> root at gumstix-custom-verdex:~/inclinometer$ /qtopia/bin/python
>>> Python 2.4.4 (#4, Apr 11 2008, 14:25:03)
>>> [GCC 4.1.2] on linux2
>>> Type "help", "copyright", "credits" or "license" for more information.
>>>>>> from PyQt4 import QtGui
>>>>>> a = QtGui.QApplication(['',"-qws"])
>>>>>> w = QtGui.QWidget()
>>> QPaintDevice::metrics: Device has no metric information
>>> Unrecognised metric -1095300876!
> I hate this kind of error. I'm sure I've seen it before. :-(
>> s=mdef%3Ainsert for the source code which prints the line. My guess is that
>> the wrong QPaintDevice is used, that is one which doesn't implement
>> metric() or maybe overloading doesn't work correctly.
> I think you're on the right track. Maybe the -qws option is not being
> passed through to the QApplication constructor correctly, in which case
> I'd pass QApplication.GuiServer as the second argument. Or perhaps, just
> speculating, the event loop needs to be started.
> Have you (Hal) tried creating and running a simple example rather than trying
> things in an interactive session?
> PyQt mailing list PyQt at riverbankcomputing.com
More information about the PyQt