Here is the thread on the similar thing. http://www.qtcentre.org/threads/10959-QWidget-Must-construct-a-QApplication-before-a-QPaintDevice
Solution seems to be: In qwtconfig.pri CONFIG += QwtDll this line must be -> #CONFIG += QwtDll When compiling. On Thu, Dec 2, 2010 at 5:24 PM, Srini Kommoori <[email protected]> wrote: > Hi Guys, > > I am trying to pack(including *so/*dylib) an app that I have with > py2app. Funny thing is, if I have Qt*.framework/ in > /Library/Frameworks, I get errors like below. > > QObject::moveToThread: Current thread (0x1004d5b20) is not the > object's thread (0x100160600). > Cannot move to target thread (0x1004d5b20) > 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. > QWidget: Must construct a QApplication before a QPaintDevice > > If I remove or move Qt*.framework, my application works fine. There > are few entries on this on Qt forum - not sure how relevant is this > here. > > I will have to come up with some way to install Qt*.framework only if > user doesn't have. Only concern is, it might create inconsistent flow. > > thanks, > -Srini > _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
