Details
-
Bug
-
Resolution: Out of scope
-
P3: Somewhat important
-
None
-
5.9.3
-
None
-
Ubuntu 17.10 / OSX 10.11 / Windows 10
Android SDK with API level 24 & 26
Android NDK 16
Configured using the command `../qt5/configure -platform win32-g++ -xplatform android-clang --disable-rpath -nomake tests -nomake examples -android-ndk C:/Android/NDK -android-sdk C:/Android/SDK -android-ndk-host windows-x86_64 -android-toolchain-version 4.9 -android-arch arm64-v8a -skip qttranslatio ns -skip qtserialport -no-warnings-are-errors -android-ndk-platform android-24 -skip qt3d -skip qtwebengine -skip qtlocation -skip qtwayland -skip qtsensors -skip qtgamepad -opengles3 -v` (with variations on paths and some fields depending on the host platform)
Ubuntu 17.10 / OSX 10.11 / Windows 10 Android SDK with API level 24 & 26 Android NDK 16 Configured using the command `../qt5/configure -platform win32-g++ -xplatform android-clang --disable-rpath -nomake tests -nomake examples -android-ndk C:/Android/NDK -android-sdk C:/Android/SDK -android-ndk-host windows-x86_64 -android-toolchain-version 4.9 -android-arch arm64-v8a -skip qttranslatio ns -skip qtserialport -no-warnings-are-errors -android-ndk-platform android-24 -skip qt3d -skip qtwebengine -skip qtlocation -skip qtwayland -skip qtsensors -skip qtgamepad -opengles3 -v` (with variations on paths and some fields depending on the host platform)
-
Android
Description
While trying to build Qt for Android ARMv8 I discovered that the openglesv3 test would fail, regardless of the values passed to the configure command line. It appears that the problem is a failure due to the GLESv3 library not being included in the link phase. This happened on Windows, OSX, and Linux, all using the Android NDK 16.
I was able to work around the issue locally by editing qtbase/mkspecs/common/android-base-tail.conf and adding `-lGLESv3` to the `QMAKE_LIBS_OPENGL_ES2` line.