Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.3
-
None
-
-
2022wk02FOAndroid&Automotive, 2022wk04FOAndroid&Automotive, 2022wk12FOAndroid&Automotive, 2022wk14FOAndroid&Automotive, 2022wk16FOAndroid&Automotive, 2022wk18FOAndroid&Automotive, 2022wk20FOAndroid&Automotive, 2022wk22FOQtforAndroid, 2022wk24FOQtforAndroid, 2022wk26FOQtforAndroid
Description
We need to start keeping better track of newer clang versions in new Android NDKs, make sure our stuff builds with them, and add them to the CI.
Verify on all target architectures x86, x86_64, armeabiv7, arm8v64
Attachments
Issue Links
- relates to
-
QTBUG-102972 [REG 6.3.0 -> 6.4.0] apps crash on Android device
- Closed
-
QTBUG-104580 androiddeployqt fails with "unknown argument '--libs'" when call llvm-readobj v14
- Closed
-
QTBUG-101318 Update to next NDK r25 LTS release
- Closed
-
QTCREATORBUG-26725 The handling of multiple Android NDKs remains confusing and awkward to use
- Reported
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...