Details
-
Bug
-
Resolution: Out of scope
-
P2: Important
-
None
-
4.7.0
-
None
-
Mac OS X 10.6.4, Qt 4.7.0 Cocoa x86.
Description
—
Cloned because the source bug is closed and I saw no way of re-opening it, and I am unsure it will be noticed by Qt team.
Check the source bug for my comments on the issue.
—
macdeploy qt adds a QtGui and QtNetwork libraries to application bundle linked against only QtCore.
Steps to reproduce:
1. Create a default console project in Qt Creator.
2. Use CONFIG+=app_bundle instead of CONFIG-=app_bundle
3. Run macdeployqt on result bundle.
I have seen in Contents/Framework:
macbook-pro-mac-pro:qtbug.app macpro$ ls Contents/Frameworks/
QtCore.framework QtGui.framework QtNetwork.framework libpng14.14.dylib
but:
macbook-pro-mac-pro:qtbug.app macpro$ otool -L Contents/MacOS/qtbug
Contents/MacOS/qtbug:
@executable_path/../Frameworks/QtCore.framework/Versions/4/QtCore (compatibility version 4.7.0, current version 4.7.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 625.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)
Workaround: use -no-plugins parameter to macdeployqt.
Attachments
Issue Links
- relates to
-
QTBUG-18172 macdeployqt puts every Qt framework in app bundle
- Closed