Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.15.0, 5.15.1
-
-
acc5e48a90d0daeccb28175b80ab6b52cac5d84a (qt/qtdeclarative/dev) f9af3434498b65ecb89bf7054c71773d066fef0b (qt/qtdeclarative/6.0) 3c075bfd348306cd553caddb9f8bf3f596666636 (qt/qtdeclarative/5.15)
Description
When building from qt-everywhere-src-5.15.1.tar.xz (and I assume the qt5.git), plugins.qmltypes files have incomplete definitions for Components when referencing types outside of the current module.
This happens because qmltyperegistrar is unable to resolve the foreign types files, resulting in (ignored) errors like these:
Cannot open foreign types file /usr/local/Qt-5.15.1/lib/metatypes/qt5gui_metatypes.json
Cannot open foreign types file /usr/local/Qt-5.15.1/lib/metatypes/qt5network_metatypes.json
Cannot open foreign types file /usr/local/Qt-5.15.1/lib/metatypes/qt5core_metatypes.json
(This example was from qtdeclarative/src/quick)
The root of this seems to be that the --foreign-types argument is being generated (in qmltypes.prf:48) using the install paths of these files and not the source tree paths. When qt is being built in a "unified" build, those files are not yet installed.
One observed symptom of this issue is that users are unable to drag-reorder qml controls in the navigator view in QtCreator
Attachments
Issue Links
- relates to
-
QTCREATORBUG-24428 When using QML_ELEMENT inside a QObject subclass with CONFIG += qmltypes then it will not be able to open the qml in design mode
- Open
-
QTCREATORBUG-24987 Editor shows Qml Module not found when using the new QML_ELEMENT registration
- Closed
-
QTBUG-85888 Qml *.qmltypes files are incomplete for android
- Closed