Details
-
User Story
-
Resolution: Done
-
P2: Important
-
None
-
6.4.0 FF
-
None
-
-
2022wk46FOQtforAndroid, 2022wk48FOQtforAndroid, 2022wk50FOQtforAndroid, 2022wk52FOQtforAndroid
Description
Building apps for platforms like Android or WebAssembly require a bunch of dependencies in addition to Qt to be ready for Qt Creator to be able to do any builds. For Android this can be an NDK, SDK platform, build-tools, etc. At the moment Qt Creator keeps a json file to track such dependencies and their versions. For example Qt 5.12 might need an NDK r19 while a Qt 6.2 needs an NDK r22b. The problem with that is that changes in Qt might not necessarily be rejected in Qt Creator, especially when using a new Qt version with an older Qt Creator version.
To fix this, we can track any dependency relations and versioning in Qt itself, and Qt Creator would merely read those. Qt Creator already uses qmake to get some information about Qt:
qmake -query
AFAIK, that gets the data from qt.conf and target_qt.conf files under bin folder of the installed Qt version.
Discussion:
The following points remain open questions for me:
- Would this approach work for various Qt platforms?
- Would qmake -query be the right way going forward, especially since we're using CMake nowadays.
- if not, we need a place that works for every build system.
This is a result of some discussions about managing NDKs in Creator, a summery on QTCREATORBUG-26725.
Attachments
Issue Links
- is required for
-
QTCREATORBUG-28426 Qt 6.5 for Android uses NDK25, QtC 9.0.0 still installs NDK23 and NDK22 on Windows 10 host
- Closed
-
QTCREATORBUG-28629 Android: Read preferred NDK version from modules/Core.json
- Closed
- relates to
-
QTCREATORBUG-28426 Qt 6.5 for Android uses NDK25, QtC 9.0.0 still installs NDK23 and NDK22 on Windows 10 host
- Closed
- resulted from
-
QTCREATORBUG-26725 The handling of multiple Android NDKs remains confusing and awkward to use
- Reported