Note: This command is in technology preview and may change in future releases.

Note: This command should only be called if targeting the Android platform.

Synopsis

qt_android_generate_deployment_settings(target)

qt6_android_generate_deployment_settings(target)

Description

The androiddeployqt tool expects a deployment settings file as input. This command reads CMake variables and properties of the target to generate such a file in the target's binary directory. Upon return, the full path to this file is available in the target's QT_ANDROID_DEPLOYMENT_SETTINGS_FILE property.

CMake Variables

A number of variables are used while generating the deployment settings file. Some are provided by Qt, others by CMake or the Android NDK.

• ANDROID_NDK_HOST_SYSTEM_NAME
• ANDROID_SDK_ROOT
• CMAKE_ANDROID_ARCH_ABI
• CMAKE_ANDROID_NDK
• CMAKE_SYSROOT
• QT_ANDROID_APPLICATION_ARGUMENTS
• QT_HOST_PATH

Target Properties

The properties below will be read from the specified target. Note that this command is called as part of target finalization (see qt_finalize_executable()). If you are using qt_add_executable() to create the target and you need to modify some of these target properties, you need to ensure that target finalization is deferred. See qt_add_executable() for how to accomplish this.

• QT_ANDROID_DEPLOYMENT_DEPENDENCIES
• QT_ANDROID_EXTRA_LIBS
• QT_ANDROID_EXTRA_PLUGINS
• QT_ANDROID_MIN_SDK_VERSION
• QT_ANDROID_PACKAGE_SOURCE_DIR
• QT_ANDROID_TARGET_SDK_VERSION
• QT_ANDROID_VERSION_NAME
• QT_ANDROID_VERSION_CODE
• QT_QML_IMPORT_PATH
• QT_QML_ROOT_PATH
• qt_no_entrypoint

Upon return, the QT_ANDROID_DEPLOYMENT_SETTINGS_FILE target property will contain the location of the generated deployment settings file.

Example

qt_android_generate_deployment_settings(myapp)
qt_android_add_apk_target(myapp)