QT_ANDROID_GRADLE_MULTI_MODULE

Builds the Android package from a multi-module Gradle project.

This variable was introduced in Qt 6.12.

Set this variable to TRUE to package an application from a Gradle project that has one module per Android artifact, an app module for the application and one module for each dynamic feature:

<build>/android-build-<target>/
    app/                    # the application module
    <feature_1_target>/     # Dynamic feature 1
    <feature_2_target>/     # Dynamic feature 2
    settings.gradle         # includes app and other dynamic features

Feature modules are what Play Feature Delivery builds on, so qt_add_android_dynamic_features() requires this variable, see qt_add_android_dynamic_feature_java_source_dirs. For a complete project that uses it, see Using Play Feature Delivery.

Set the variable when configuring the project:

qt-cmake -S <source_dir> -B <build_dir> -DQT_ANDROID_GRADLE_MULTI_MODULE=ON

or early on before qt_add_executable() so that it is known before the executable is created:

set(QT_ANDROID_GRADLE_MULTI_MODULE ON)

The variable also decides what builds the package. By default, CMake writes a deployment settings file and hands the rest to androiddeployqt, which resolves the Qt dependencies, copies them into the build directory, and runs Gradle from there. With the variable enabled, CMake deploys the dependencies itself as regular build steps and generates the Gradle files of every module. The apk and aab targets then run Gradle directly, and androiddeployqt isn't involved at all. The application is packaged from android-build-<target>/app, and the deployed files are build dependencies of the package. This option is generally faster and simpler since it relies on the CMake build graph and doesn't rely on additional deplyoment tools.

The variable is available since Qt 6.11 as QT_USE_ANDROID_MODERN_BUNDLE. That name is deprecated since Qt 6.12, but is still honored if set.