Details
-
User Story
-
Resolution: Fixed
-
P2: Important
-
None
-
None
Description
Split out of QTBUG-95024, which is about providing a lower level CMake API than that discussed here.
To make installation simpler for user projects, we want to provide a higher level CMake API that allows installation (and in the case of macOS app bundles, post-build rules to allow running apps from the build tree) of Qt libraries, plugins and QML modules (at least the qmldir files and the plugins). The higher level API should be reasonably easy for less experienced users to employ and adapt in their project based on canonical examples for common cases.
Attachments
Issue Links
- is required for
-
QTBUG-102057 Use CMake deployment API in Qt examples once the API is out of TP
- In Progress
- relates to
-
QTBUG-52798 Unify the *deployqt tools into a host tool in qtbase
- Closed
-
QTBUG-74940 Provide a deployment tool for Linux
- Reported
-
QTBUG-102595 Builds can't find the projects qml modules
- Closed
-
QTBUG-102056 Remove usage of INSTALL_EXAMPLESDIR and INSTALL_EXAMPLEDIR in examples
- Reported
-
QTBUG-104554 Revisit our story about the default qml import path for macOS app bundles
- Reported
-
QTBUG-101338 Investigate removing usage of symlinks for QML modules in macOS app bundles
- Reported
-
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
-
QTBUG-104876 Enable qt_deploy_qml_imports() to support libraries
- Reported
-
QTBUG-90820 Build examples as external projects within the main build
- In Progress
-
QTBUG-96289 Research, improve and potentially unify Qt application deployment story around CPack
- Closed
- resulted from
-
QTBUG-95024 Offer CMake API to get a list of qml module artifacts for installation purposes
- Closed
- resulted in
-
QTBUG-100102 Provide CMake API for deploying a single QML module
- Reported