Alex Elliott - 2016-03-08

Hi,

I've been trying to set up a build system which for legacy reasons includes multiple concurrent Qt versions - and we've in the past had to rely on a bodge with an explicit /usr/plugins symlink because macdeployqt when going over our bundle won't find the plugin directory otherwise. With multiple Qt versions that's not going to cut it however so I've gone into our application to find out what's going on.

It appears from what I can tell that linking libPythonQt.dylib to our application is what triggers the change in behaviour from macdeployqt. I took an example program (clocks from Qt Creator's examples) and the stock PythonQt 3.0 with our Qt5.5/Yosemite build machine - and just adding that library to LIBS triggers the same behaviour.

I've got a log of the -verbose=3 output of macdeployqt for the clocks demo with PythonQt linked here:

https://gist.github.com/anonymous/3b00432ec63bbf8af689

Obviously without any of the plugins such as the platform plugin any such bundle will fail to run. So I would be keen to find some way to get around this if possible, whether that's something on the PythonQt side or the macdeployqt side I don't know.

Cheers,
Alex