Changing ABI doesn't modify effective qmake call
-
On QT 5.15.14 it's working correctly with ANDROID_ABIS="armeabi-v7a arm64-v8a"
When I switched to QT 5.15.15 it only shows ANDROID_ABIS="arm64-v8a"
What do I need to do to get this additional armeabi-v7a in there? Previously I just checked the box and the effective qmake call would update, but now this doesn't work. I have the same issue on my Mac, I checked ARM and x86 on there and it also won't update this qmake call.
-
@Bradyok So I had the same issue. However, it appears to be a Qt Creator related issue (possibly a bug!?).
What you can do is setANDROID_ABIS="arm64-v8a armeabi-v7a"in your qmake.profile (or in CMake).Also, you can change it inside the
.pro.userfile by modifying the value ofQtProjectManager.QMakeBuildStep.SelectedAbiskey (although this is only a temporary solution).Unfortunately, I haven't found any other solutions for this problem.
-
On QT 5.15.14 it's working correctly with ANDROID_ABIS="armeabi-v7a arm64-v8a"
When I switched to QT 5.15.15 it only shows ANDROID_ABIS="arm64-v8a"
What do I need to do to get this additional armeabi-v7a in there? Previously I just checked the box and the effective qmake call would update, but now this doesn't work. I have the same issue on my Mac, I checked ARM and x86 on there and it also won't update this qmake call.
Hi @Bradyok, and welcome!
Yes, it's a bug in Qt Creator 11.0.2: https://bugreports.qt.io/browse/QTCREATORBUG-29506 It will be fixed in v11.0.3.
In the meantime, you can install and use v11.0.1: https://download.qt.io/official_releases/qtcreator/11.0/11.0.1/ or use @S_M_R's workaround
