Restrict macdeployqt to only deal with Qt dependencies
-
I just updated Qt from 6.2 to 6.6. On 6.2 on MacOS,
macdeployqtonly added the required Qt dependencies to the Framework directory. Now, it also adds dependencies that are unrelated to Qt. Unfortunately it does not do the right things on several binaries that rely on other 3rd party resources. Is there a way to get the old behavior back? -
Hi and welcome to devnet,
Which new dependencies are you getting ?
-
One of the issues is that a plugin of my code relies on XQuartz. macdeployqt gets the .dylibs from XQuartz into the bundle. This is first of all useless as one needs the full XQuartz app to be able to use X11 and second, it messes up the digital signature of Xquarz, which prevents using it completely. Similar, but not fully investigated issue happens with the Python plugin.
With Qt 6.2, Qt did only the Qt resources and I had a similar script to deal with the plugin dependencies, but not all of them as some are deliberately not included into the bundle. That is probably a little atypical.
I'm now planning to wrap the script, by first moving the plugin directory to outside the bundle, run
macdeployqt, move the plugins back and do my own thing. Not great :(
