Details
-
Task
-
Resolution: Done
-
P3: Somewhat important
-
6.4.0 RC1
-
None
-
727151e0e0 (qt/qtdeclarative/dev) 727151e0e0 (qt/tqtc-qtdeclarative/dev) 96182610b8 (qt/qtdeclarative/6.4) 5b35a32ecc (qt/qtdeclarative/6.3) 5b35a32ecc (qt/tqtc-qtdeclarative/6.3) 96182610b8 (qt/tqtc-qtdeclarative/6.4) 121107c01d (qt/qtdeclarative/6.4.0)
Description
This shows up when trying to build examples as external projects in the CI which uses a prefix build: QTBUG-96232
qtdeclarative is built, but not installed, and the example external projects are using the export(EXPORT) build time Config files.
While the build dir CMake packages themselves are found, _qt_internal_scan_qml_imports passes ${QT6_INSTALL_PREFIX}/${QT6_INSTALL_QML} as an -importPath argument which ends up empty, because qtdeclarative is not installed yet.
It would be nice to make this scenario work, so that the example external projects are actually runnable in a prefix build.
This might also affect in-tree tests, but haven't confirmed yet.
This was discussed a few times internally and also in some jira issues.
We already do something similar (ensuring build time import paths are found in a prefix build) when building Qt itself for qmllint / qmltc via the _qt_internal_extend_qml_import_paths function.
Attachments
Issue Links
- is required for
-
QTBUG-96232 Figure out how to build examples as ExternalProjects in a prefix build setup so it can be used in the CI
- In Progress
- relates to
-
QTBUG-98011 qmltc crashes due to insufficient import locations in a specific Qt build configuration
- Closed