-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.8.4, 6.9.1, 6.10.0 Beta2
-
None
-
-
a5028fe2d (dev), 6e936f470 (6.10), 381468e2e (6.9), 0f504076c (tqtc/lts-6.8)
-
2025wk34s2QtforAndroid
Starting with https://codereview.qt-project.org/c/qt/qtbase/+/596169
the build system generates a wrapper script to allow to easily launch an android app.
In certain projects the wrapper script and a qml module's directory name can clash, resulting in the wrapper script not being created, or worse, changing the permissions of the build dir removing write access, causing weird build errors.
An example is the hangman demo from qtdoc repo.
We should either consider renaming the wrapper script (and its uses in Qt Creator) to not conflict with the subdirectory name.
Or modify such projects to have a different app name and URI, and try to warn when such a case is detected.
Detecting such a case is difficult though, especially if it's not due to qml modules, but just a regular add_subdirectory() call. Cmake doesn't do us any favors in this case.
In case of the hangman project, it does set the OUTPUT_NAME of the app target to something else, so it doesn't conflict. In this respect the fact that _qt_internal_android_create_runner_wrapper doesn't read it is a bug. But if we teach it to follow what OUTPUT_NAME says, we still need to modify Qt Creator, and older Creators will fail to find the file for older Qts.
- resulted from
-
QTBUG-138565 "Cannot generate qmltypes file" when trying to run in-app purchase demo app on Android
-
- Closed
-
- resulted in
-
QTCREATORBUG-33364 Support OUTPUT_NAME and RUNTIME_OUTPUT_DIRECTORY when running Android tests
-
- Reported
-