Priority: P1: Critical
Affects Version/s: 5.14.0
Fix Version/s: None
Component/s: Build System
Environment:Android NDK 20.x, linux.
I suspect the problem appeared after compilation for several target android platforms at once was introduced (-android-abis option). At the moment, if I try to compile for arm32 only (with option -android-arch=armeabi-v7a ) --: the compilation fails, because building system tries to build for aarch64 target platform: which is weird.
In order to get a build done I manually edit qtbase/mkspecs/features/android/default_pre.prf file and change lines:
and then compilation for armeabi-v7a only works.
Obviously when I specify - android-arch=armeabi-v7a (I dont specify - android-abis configure option ): it should just work, without this manual intervention into source code of build system.
The other obvious thing (and reason why I can't use -android-abis option) is that new approach wasn't thought through: I cant compile qt for arm32 and arm64 if I use any outside statically linked library, namely openssl in my case.
At the moment I have two separate compilations of openssl for arm32 and arm64 with different paths for each, and use them for two separate compilations of qt.
In other words: I cant provide different -I or -L options for configure, different for each target android platform, if I was to use -android-abis options.