On Fri, 21 Nov 2008, Christopher Barker wrote:
Jeremy Sanders wrote:
Thanks for the reminder. Using the latest development version fixes the
nasty uic issue - I only had to manually include the sip package.
good to hear -- I wonder why the sip recipe didn't work? Any chance you
can figure it out and provide a patch?
Sorry for the delay - it's because the sip recipe isn't being run because
it's not included in the recipes __init__.py file.
The recipe wasn't being run at all. However, just adding sip to the
package list seemed to be enough to get my application working.
I'm having an additional problem. One of my users is reporting that his Qt
is being loaded at the same time as the packaged one. The error messages
are:
QObject::moveToThread: Current thread (0x269d8c0) is not the object's
thread
(0x1e45b0).
Cannot move to target thread (0x1e45b0)
On Mac OS X, you might be loading two sets of Qt binaries into the same
process. Check that all plugins are compiled against the right Qt
binaries.
Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are
being loaded.
QObject::moveToThread: Current thread (0x269d8c0) is not the object's
thread
(0x1e45b0).
Cannot move to target thread (0x1e45b0)
Any idea what was causing this? The supplied app didn't have the proper
sip recipe applied to it. Would this have stopped this problem?
Thanks
Jeremy
--
Jeremy Sanders <[EMAIL PROTECTED]>
http://www.jeremysanders.net/ Cambridge, UK
Public Key Server PGP Key ID: E1AAE053
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
