Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.5.0 Beta1
-
ce8874fc3 (dev), 47b879aa0 (dev), ba3cc0a09 (dev)
Description
Consider the attached example. The user is trying to link a number of static libraries that formally contain Qt resources into an application. When doing this via the CMake build system, the resources are lost as they reside in separate object libraries that you cannot link this way.
How did this work in qmake?
Attachments
Issue Links
- is duplicated by
-
QTBUG-110075 Linker failure when using Q_IMPORT_QML_PLUGIN() on external static QML plugin
- Closed
-
QTBUG-115167 Issues statically linking extension plugin on Windows Qt6
- Closed
- relates to
-
QTBUG-97816 Prevent linker from discarding unused shared libraries
- Reported
-
QTBUG-91448 Undefined resource symbols when linking app with a static Qt without qmake and CMake
- Closed
-
QTBUG-80863 [cmake] excessive compilation of Import.cpp files for static plugins
- Closed
-
QTBUG-100102 Provide CMake API for deploying a single QML module
- Reported
- split from
-
QTBUG-110110 Problems writing QML Modules
- Closed
- mentioned in
-
Page Loading...