Hi David, On 23/01/15 10:14, David Cortesi wrote: > Apologies for a messed-up report earlier. I had attempted pyinstaller -w > myscript.spec, but the spec file was left over from previous runs that did not > specify -w. My bad. > > When I ran pyinstaller -w -i iconfile.icns myscript.py, a correct Mac OS app > folder was created, it even sported the desired icon. So MacOS bundle is in > and > working for python 3. > > But when double-clicked, the app failed with SIGABRT. Running from the command > line, myscript.app/Contents/MacOS/myscript produces the console message, > >> This application failed to start because it could not find or load the Qt > platform plugin "cocoa". >> Reinstalling the application may fix this problem. >> Abort trap: 6 > > "find -name '*oco*'" gets no hits in the .app folder. Searching the files in > the > build folder, I do not find the string "oco" in any of the files, the warn > file > or any of the out00-* files.
That still looks like your problem - PyInstaller appears to not be packaging libqcocoa.dylib. Does libqcocoa.dylib exist in your Qt installation? Do the logs show any warnings that it couldn't be found? > > Using otool -L Qt* | grep oco shows that four of the Qt DLLs refer to > /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa but that should > not > be a problem. None of the Py*.so files refer to "oco" on this test. I don't think you should expect the Py*.so to refer to the Cocoa libs. The Qt libs should link to Cocoa as your output shows. 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.
