Qt for Android CMake Configuration
This page lists information regarding CMake and Qt for Android platform support.
Variables affecting the build process
This is a list of CMake variables or properties that affect the build process including Gradle configuration:
| List of ABIs that packages of a single target are built for | |
| List of ABIs that the project packages are built for | |
| Enables building multi-ABI packages using the autodetected Qt for Android SDK list | |
| Overrides the Qt dependencies added to the target's deployment | |
| Specifies the location of a target's generated deployment settings file | |
| Forces or disables release package signing regardless of the build type | |
| Extra libraries to deploy with the target | |
| Extra Qt plugins to deploy with the target | |
| Enables the generation of QtQuickViewContent-based classes | |
| Minimum Android SDK version | |
| Allows to share CMake variables in multi-ABI builds | |
| Whether Qt shared libraries are packaged in the APK on Android | |
| App's package name | |
| Path to a custom Android package template | |
| Revision of Android build tools to use | |
| Signs the .aab package with the specified keystore, alias, and store password | |
| Signs the package with the specified keystore, alias, and store password | |
| Specifies the location of Qt libraries on the target device | |
| Android target SDK version | |
| Marks a QML file for Java code generation | 
Variables affecting the Android app manifest file
This is a list of CMake variables or properties that can set some of the Android Manifest's configuration directly from CMake without having to manually set them in the manifest.
| List of arguments to pass to Android applications | |
| Internal Android app version | |
| Human-readable Android app version |