Installation and Deployment

Very nice to know!

@Zola Hi, The libqxcb.so file that reside inside platforms folder (in your application package, and I'm assuming you are dynamically linking with qt ) needs additional dependencies. You can find all dependencies by calling ldd for libqxcb.so, but we need to copy files reside only in Qt directory. Find it in Qt libs directory ( in my case it was libQt5DBus.so.5). Change name (*.so.5.4.1 to *.so.5) and copy it to executable directory.

@AKstatistics Solved my own problem. Cross posted on Stack Overflow http://stackoverflow.com/q/34056095/4179820

Great :-) Happy coding!

@dvb0222 I had a similar need for installing Qt using a Dockerfile script. Check out my solution here: http://stackoverflow.com/a/34032216/471839

Please try to go through these steps : Chapter 7 and this Chapter 11

I'll suggest that you print some environment variables to check if the paths for the shared libraries are OK. So, from the environment you are trying to execute your python script, try to print PATH, PYTHONPATH and DYLD_LIBRARY_PATH Even better, you can try to print this from your python script with something like this import os print os.environ['PATH'] print os.environ['DYLD_LIBRARY_PATH'] print os.environ['PYTHONPATH'] The check if the missing path is listed somewhere

Hi, Which module do you to build or not ? Also what sources are you using ? The one from git or the one provided by the installer ?

I found the answer. The problem is that the QtWebKit.framework bundle requires some of these other ones, even though I might not be using them. The only fix would be to acquire the QtWebKit.framework project, remove the QML and Quick dependencies, recompile, swap that framework bundle out of my project after macdeployqt, and then remove the QML and Quick framework bundles. Long story short, that ain't happening. Not worth my time because it's super difficult.

You should take a look at this thread. The poster has provided links to an interesting Wiki to build everything you need before building Qt.

Like this: ./configure -skip sensors -skip location -skip multimedia ... By default, it compiles everything.

Yes, Qt is kind of braindead :-) before QApplication a(argc, argv); not many things work; it tries to load the libqcocoa.dylib when you specify that Fusion setting line, and because you did it before the QApplication constructor, Qt hasn't found and read in qt.conf file (written by macdeployqt, it tells Qt where to find libqcocoa.dylib). That's why moving the Fusion setting after makes Qt much happier. P.S. Actually you can get around this error in another way than by moving the Fusion setting line: by copying the PlugIns folder (created by macdeployqt in example.app) and place it together with the .exe/ELF file (MacOs/example). Because then Qt can load the Cocoa plugin without having read any qt.conf file.

@d.terhaar Thanks! This fixed me on this post: https://forum.qt.io/topic/61001/broken-qt-5-5-macdeployqt/3 I moved my Fusion style line AFTER the QApplication a(argc, argv); line, unlike previous documentation I had read for this, and the problem went away. I was now able to deploy without Cocoa issues. I had been racking my brains for 3 hours on this. I'm so glad you did the difficult digging to find the fix.

Thank you. It worked!!!