Priority: P2: Important
Resolution: Cannot Reproduce
Affects Version/s: 5.5.0
Fix Version/s: None
Component/s: Build tools: Other
Hi, I can't compile Qt for Android since the last version of Android SDK. I need to test ad old version of Android in SDK, so this is important for me (and for anyone who installed Qt to compile for Android recently).
I use Kubuntu 14.04 and I have the g++-arm-linux-gnueabihf package installed and the compilers (with Android NDK and SDK) are correct. I tried the Oracle JDK and OpenJDK without any result, the same procedure for Ant, I reset all configurations and tried Gradle without getting any good result.
I uploaded the package I have installed in Android SDK, and Qt Creator shows this text every time I try to compile for Android.
[mergemanifest] Merging AndroidManifest files into one.
[mergemanifest] Manifest merger disabled. Using project manifest only.
[echo] Handling aidl files...
[aidl] Found 2 AIDL files.
[aidl] Compiling 2 AIDL files.
[echo] Handling RenderScript files...
[echo] Handling Resources...
[aapt] Generating resource IDs...
[aapt] /home/edu/Qt/build-tryingbug-Android_for_armeabi_v7a_GCC_4_9_Qt_5_5_0-Debug/android-build/bin/AndroidManifest.xml:4: error: Error: String types not allowed (at 'configChanges' with value 'orientation|uiMode|screenLayout|screenSize|smallestScreenSize|layoutDirection|locale|fontScale|keyboard|keyboardHidden|navigation').
/home/edu/bin/Java-sdkAndroid/android-sdk-linux/tools/ant/build.xml:649: The following error occurred while executing this line:
/home/edu/bin/Java-sdkAndroid/android-sdk-linux/tools/ant/build.xml:694: null returned: 1
Total time: 1 second
Building the android package failed!
– For more information, run this command with --verbose.
17:19:53: The process "/home/edu/bin/Qt5-Dev/5.5/android_armv7/bin/androiddeployqt" exited with code 14.
Error while building/deploying project tryingbug (kit: Android for armeabi-v7a (GCC 4.9, Qt 5.5.0))
When executing step "Build Android APK"
This is not the first time I see a similar bug, but in the previous case it was repaired by Google updating the Android SDK.