On 26/01/15 15:11, David Cortesi wrote: > I learned that exporting QT_DEBUG_PLUGINS might get some info, and it did. The > app says it is checking directory path > ".../dist/cobro.app/Contents/MacOS/qt5_plugins/platforms". > > "qt5_plugins" ??? Where does THAT come from?
It comes from loader/rthooks/pyi_rth_qt5plugins.py . I have no idea why it is named that way though. I did tell you at the beginning of this thread that it was looking there: On 17/01/15 10:13, David Cortesi wrote: > I said that under Python 3, pyinstaller made a one-folder bundle of my PyQt5 > app that failed with the message, > >> This application failed to start because it could not find or load the Qt > platform plugin "cocoa". > > Glenn Ramsey said, > >> On my build it looks like this: >> My.app/Contents/MacOS/qt5_plugins/platforms$ otool -L libqcocoa.dylib... > OK, just to make sure everything was clean I reran pyinstaller. Moved > libqcocoa.dylib into Contents/MacOS/qt5_plugins/platforms. > > And the app started. taa-bleeping-daa! > > So apparently this is what it takes to let Qt 5.4 find its platform plugin. > See > preceding note for everything I tried that didn't work. The question now is: why did PyInstaller fail to do this automatically in your case? Could it be related to Qt/PyQt 5.4? Glenn -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
