qiurui
/
qtdeclarative
mirror of https://github.com/qt/qtdeclarative.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
qtdeclarative/examples/core/permissions/CMakeLists.txt

58 lines
1.4 KiB
CMake
Raw Permalink Normal View History

Add QML API for application permissions The API is based on dedicated QML types for each permission type, where each instance of the permission reports status separately. Requests for permissions are done imperatively for now, as the semantics of a declarative request were hard to nail down, and the user can easily build a declarative flow on top of the imperative API that fits their needs and semantics. Task-number: QTBUG-111001 Done-with: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Change-Id: I0ebc99e0fa0d22b0af5aa1d34851c5f0c62357c0 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
2023-02-17 14:50:14 +00:00
# Copyright (C) 2023 The Qt Company Ltd.
Correct license for examples files Example takes precedent over build system file type. According to QUIP-18 [1], all examples file should be LicenseRef-Qt-Commercial OR BSD-3-Clause [1]: https://contribute.qt-project.org/quips/18 Pick-to: 6.7 6.7.0 Task-number: QTBUG-121787 Change-Id: Ie8c2539e7659f53a1fd6b48f99ee883ee9aeb0a7 Reviewed-by: Kai Köhne <kai.koehne@qt.io>
2024-03-07 14:22:17 +00:00
# SPDX-License-Identifier: LicenseRef-Qt-Commercial OR BSD-3-Clause
Add QML API for application permissions The API is based on dedicated QML types for each permission type, where each instance of the permission reports status separately. Requests for permissions are done imperatively for now, as the semantics of a declarative request were hard to nail down, and the user can easily build a declarative flow on top of the imperative API that fits their needs and semantics. Task-number: QTBUG-111001 Done-with: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Change-Id: I0ebc99e0fa0d22b0af5aa1d34851c5f0c62357c0 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
2023-02-17 14:50:14 +00:00
cmake_minimum_required(VERSION 3.16)
project(permissions LANGUAGES CXX)
set(CMAKE_AUTOMOC ON)
CMake: Fix examples built as external projects Usage of a private module needs a respective find_package call now. Change-Id: I20f7571e11ab9b2ca6d185b4834e72100d9ce2d6 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2025-01-29 13:30:52 +00:00
find_package(Qt6 REQUIRED COMPONENTS CorePrivate Gui Quick QuickControls2)
qt_standard_project_setup(REQUIRES 6.9)
Add QML API for application permissions The API is based on dedicated QML types for each permission type, where each instance of the permission reports status separately. Requests for permissions are done imperatively for now, as the semantics of a declarative request were hard to nail down, and the user can easily build a declarative flow on top of the imperative API that fits their needs and semantics. Task-number: QTBUG-111001 Done-with: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Change-Id: I0ebc99e0fa0d22b0af5aa1d34851c5f0c62357c0 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
2023-02-17 14:50:14 +00:00
qt_add_executable(permissions
main.cpp
)
qt_add_qml_module(permissions
URI PermissionsExample
QML_FILES
"Main.qml"
)
target_link_libraries(permissions PUBLIC
Qt::Core
Qt::CorePrivate
Qt::Gui
Qt::Quick
Qt::QuickControls2
)
if(UNIX AND NOT APPLE AND CMAKE_CROSSCOMPILING)
find_package(Qt6 REQUIRED COMPONENTS QuickTemplates2)
# Work around QTBUG-86533
target_link_libraries(permissions PRIVATE Qt::QuickTemplates2)
endif()
set_target_properties(permissions PROPERTIES
MACOSX_BUNDLE TRUE
MACOSX_BUNDLE_INFO_PLIST "${CMAKE_CURRENT_SOURCE_DIR}/Info.plist"
MACOSX_BUNDLE_GUI_IDENTIFIER "io.qt.examples.qmlpermissions"
QT_ANDROID_PACKAGE_SOURCE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/android"
)
install(TARGETS permissions
CMake: Add deployment API to our examples Projects were modified using the tool at: https://git.qt.io/alcroito/cmake_refactor A few examples had to be adapted manually, mostly those that build additional qml modules / plugins. The INSTALL_EXAMPLESDIR and INSTALL_EXAMPLEDIR assignments were removed, these are not needed anymore because example directory selection is handled by the qt_internal_add_example calls. The install(TARGETS) calls were modified according to our documentation snippets for qt_generate_deploy_qml_app_script. A qt_generate_deploy_qml_app_script call was added for each executable target. Note that the deployment step will be skipped in the CI for now, because: - we enable QT_DEPLOY_MINIMAL_EXAMPLES in the CI instructions and thus set QT_INTERNAL_SKIP_DEPLOYMENT to true - standalone examples feature is not yet enabled in the CI, which means we continue to build examples in-tree, and deployment is disabled for in-tree prefix builds. A small list of examples to deploy in the CI will be chosen in the future, to ensure deployment coverage, without slowing down overall CI times due to all the *deployqt invocations. Even if deployment is disabled in the CI, the install(TARGETS) calls for each example will still run, installing into an 'installed_examples' directory, which will not be archived by the CI. The QtBundleQmlModuleForMacOS and bundle_shared code was removed, because we can now depend on the MACOS_BUNDLE_POST_BUILD option of the deployment api, to ensure macOS bundle examples run properly in the build dir. This works even in prefix in-tree builds, when installation deployment is disabled. Finally, for all examples that build additional qml module libraries or plugins, the libraries / plugins must be installed into the bin dir of each project, along with a qmldir file. This is to support running the installed project for platforms that don't have deployment api yet, like boot2qt / yocto. If we want to have super clean install / deployment rules in the future, we won't be able to avoid adding ugly per-platform conditions. The current status quo is deemed an improvement over what we had before. Pick-to: 6.7 Task-number: QTBUG-101340 Task-number: QTBUG-102056 Task-number: QTBUG-102057 Change-Id: I843d934668c25dbcd1abca52495b393579633fc5 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
2024-03-18 18:03:03 +00:00
BUNDLE DESTINATION .
RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
)
qt_generate_deploy_qml_app_script(
TARGET permissions
OUTPUT_SCRIPT deploy_script
MACOS_BUNDLE_POST_BUILD
NO_UNSUPPORTED_PLATFORM_ERROR
DEPLOY_USER_QML_MODULES_ON_UNSUPPORTED_PLATFORM
Add QML API for application permissions The API is based on dedicated QML types for each permission type, where each instance of the permission reports status separately. Requests for permissions are done imperatively for now, as the semantics of a declarative request were hard to nail down, and the user can easily build a declarative flow on top of the imperative API that fits their needs and semantics. Task-number: QTBUG-111001 Done-with: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Change-Id: I0ebc99e0fa0d22b0af5aa1d34851c5f0c62357c0 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
2023-02-17 14:50:14 +00:00
)
CMake: Add deployment API to our examples Projects were modified using the tool at: https://git.qt.io/alcroito/cmake_refactor A few examples had to be adapted manually, mostly those that build additional qml modules / plugins. The INSTALL_EXAMPLESDIR and INSTALL_EXAMPLEDIR assignments were removed, these are not needed anymore because example directory selection is handled by the qt_internal_add_example calls. The install(TARGETS) calls were modified according to our documentation snippets for qt_generate_deploy_qml_app_script. A qt_generate_deploy_qml_app_script call was added for each executable target. Note that the deployment step will be skipped in the CI for now, because: - we enable QT_DEPLOY_MINIMAL_EXAMPLES in the CI instructions and thus set QT_INTERNAL_SKIP_DEPLOYMENT to true - standalone examples feature is not yet enabled in the CI, which means we continue to build examples in-tree, and deployment is disabled for in-tree prefix builds. A small list of examples to deploy in the CI will be chosen in the future, to ensure deployment coverage, without slowing down overall CI times due to all the *deployqt invocations. Even if deployment is disabled in the CI, the install(TARGETS) calls for each example will still run, installing into an 'installed_examples' directory, which will not be archived by the CI. The QtBundleQmlModuleForMacOS and bundle_shared code was removed, because we can now depend on the MACOS_BUNDLE_POST_BUILD option of the deployment api, to ensure macOS bundle examples run properly in the build dir. This works even in prefix in-tree builds, when installation deployment is disabled. Finally, for all examples that build additional qml module libraries or plugins, the libraries / plugins must be installed into the bin dir of each project, along with a qmldir file. This is to support running the installed project for platforms that don't have deployment api yet, like boot2qt / yocto. If we want to have super clean install / deployment rules in the future, we won't be able to avoid adding ugly per-platform conditions. The current status quo is deemed an improvement over what we had before. Pick-to: 6.7 Task-number: QTBUG-101340 Task-number: QTBUG-102056 Task-number: QTBUG-102057 Change-Id: I843d934668c25dbcd1abca52495b393579633fc5 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
2024-03-18 18:03:03 +00:00
install(SCRIPT ${deploy_script})