Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.7
-
None
-
0cd35272fcece740f94841a07081e1c6ab5b4fed
Description
If e.g. the Material style is not explicitly imported (in a static build) in QML, the plugin won't be picked up by qmake/qt.prf's static QML import support and the default style will be used instead.
Either users explicitly import the styles they wish to use with the application, or we add dependencies to each style to controls' qmldir so that they don't need to. The latter is not really an option, because it means they'd get plugins they didn't ask for. So, we should document this for users who are doing static builds.
Attachments
Issue Links
- is duplicated by
-
QTBUG-60680 iOS: only default style available
- Closed
- is required for
-
QTBUG-50456 Improve deployment: "make deploy"
- Reported
- relates to
-
QTBUG-38735 QML applications fail to detect default module plugins
- Open
-
QTBUG-38296 Allow blacklisting unneeded libraries or plugins
- Closed
-
QTBUG-61580 unwanted dependies for unused QtQuickControls2 styles
- Closed
For Gerrit Dashboard: QTBUG-52466 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
155214,9 | Add deployment documentation | 5.7 | qt/qtquickcontrols2 | Status: MERGED | +2 | 0 |
316632,9 | Document that styles must be explicitly imported for static builds | dev | qt/qtquickcontrols2 | Status: MERGED | +2 | 0 |
328687,2 | Document that styles must be explicitly imported for static builds | 6.0 | qt/qtquickcontrols2 | Status: MERGED | +2 | 0 |