Details
-
User Story
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
-
None
-
Android
Description
- Add CMake build targets to handle app signing, this can be part of the targets to build APKs, etc. based on the user choice. This target could be using the various singing tools (apksigner, jarsigner and zipalign).
- One of the good approach for this also is to have a separate target to handle signing directly, that way an app could be signed without doing a full build, as is the case now with androiddeployqt.
- Under this, consider reworking or keeping the functionality of QT_ANDROID_DEPLOYMENT_TYPE to allow mixing of debug/release artifacts between C++ and Java/Kotlin.
- And since this work to modernize things, we need to start supporting modern signing ways in addition to the existing param and environment variable based options, but including support for Gradle based signing properties as detailed in https://developer.android.com/studio/publish/app-signing#secure-shared-keystore.