Why does macdeployqt create a frameworks dir..

[PSI-lbc]

Why does macdeployqt create a frameworks directory populated with parts of the Qt framework not used by the Application?

I do "otool -L appbundle" and the output lists a few Qt frameworks I know are used by the application.

When I run "macdeployqt appbundle" the framework is populated with most if not all Qt frameworks and a boatload of plugins regardless of whether the application actually uses them or not.

Is it safe to delete the Qt frameworks from the Appbundle/Frameworks directory not listed in the otool output?

Is there a command line option for macdeployqt that I'm missing?

I don't want to deploy unnecessary frameworks if they aren't required.

[jakepetroules]

This is a known issue. It's been fixed in Qt 5. See:

https://bugreports.qt-project.org/browse/QTBUG-14699
https://bugreports.qt-project.org/browse/QTBUG-18172
https://bugreports.qt-project.org/browse/QTBUG-18189

[PSI-lbc]

Thx for the reply. Is there a way to address this short of upgrading to Qt 5 ?

I'm using 4.7.3 and would prefer to not change horses mid-stream...

[SGaist]

You can safely remove everything that is not used/linked to your application from the bundle.
Also, if you have external dependencies, check that their path are set to use what's inside your bundle (i.e otool -L)