Details
-
Sub-task
-
Resolution: Fixed
-
P2: Important
-
None
-
Android
Description
Document the available ABI values on each documentation page with something like
"These are the common values: a,b,c"
Add overview documentation for how all of these ANDROID vars and properties interact. Use blog post as inspiration.
Semi-related, mention in documentation that qt_add_library + Android for an SDK use case is currently not supported.
Mention in docs that qt_add_application + qt_add_library linked into the application works
Investigate and see if it's possible to implement a diagnostic: if an app is built with 2 abis, but a library it links to with only one abi, we should show an error at CMake time, rather than androiddeployqt time.
Attachments
| For Gerrit Dashboard: QTBUG-100208 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 392273,9 | Add the list of supported Android ABIs to the related documentation | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 392562,10 | Document building user project using Android Multi-ABI | dev | qt/qtdoc | Status: MERGED | +2 | 0 |
| 393579,2 | Add the list of supported Android ABIs to the related documentation | 6.3 | qt/qtbase | Status: MERGED | +2 | 0 |
| 393620,2 | Document building user project using Android Multi-ABI | 6.3 | qt/qtdoc | Status: MERGED | +2 | 0 |
| 394353,3 | Mention that the QT_ANDROID_ABIS property only affects executable targets | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 394931,2 | Mention that the QT_ANDROID_ABIS property only affects executable targets | 6.3 | qt/qtbase | Status: MERGED | +2 | 0 |