macdeployqt also includes debug libs in the app bundle (even for a release build)

[Nihilish]

Our Qt app is built by a CI machine. Recently we updated our Qt version to 5.15.11 and started making universal builds for MacOS. At the end of our pipeline, we run macdeployqt on the build but since we upgraded to 5.15.11, we noticed macdeployqt was also adding debug versions of the Qt libraries to our app bundle. This is a release build, so we don't need the debug libraries. I saw that there's a -use-debug-libs argument to include those libs (which we're not using). Is there a similar argument to prevent macdeployqt from adding these libs?

[SGaist]

Hi,

5.15.11 being currently commercial only I would recommend contacting the Qt Company directly.

In between, is it something that you observed between Qt 5.15.10 and 5.15.11 ?

[Nihilish]

Hey!

We were using 5.15.8 before and we didn't have the debug libs in our app bundle. It might have something to do with our new Qt install. A lot of the library files in the qml subfolder are suffixed by _debug.

[SGaist]

You can have both builds co-existing but macdeployqt should only take the ones used to build your application.

Can you run otool -L against your application executable to check which librairies it is linked against.