Details
-
Bug
-
Resolution: Done
-
Not Evaluated
-
Qt Creator 3.0.1
-
None
-
Linux Mint 16 x64
Windows 7 32bit
Windows 8.1 x64
Description
I was using Qt Creator frequently for developing Qt Apps for Android under Linux Mint 16 ×64 but when I tried to use Qt Creator 3.0.1 (bundled with Qt 5.2.1) It became unable to see Android’s SDK and NDK! So I created a fresh user then did exactly the mentioned steps in Qt Creator guide
- I already updated android-sdk_r22.6.2-linux to recent version
- I use android-ndk-r9d-linux-x86_64
- Although I’m sure that I configured QC correctly as mentioned in the screenshot I got this error:
/bin/sh: 1: /opt/android/ndk/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin/arm-linux-androideabi-gcc: not found Project ERROR: You need to set the ANDROID_NDK_ROOT environment variable to point to your Android NDK. Could not read qmake configuration file /home/mbnoimi/.Qt5.2.1/5.2.1/android_armv5/mkspecs/android-g++/qmake.conf. /bin/sh: 1: /opt/android/ndk/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin/arm-linux-androideabi-gcc: not found Project ERROR: You need to set the ANDROID_NDK_ROOT environment variable to point to your Android NDK. Could not read qmake configuration file /home/mbnoimi/.Qt5.2.1/5.2.1/android_armv7/mkspecs/android-g++/qmake.conf. /bin/sh: 1: /opt/android/ndk/toolchains/x86-4.8/prebuilt/linux-x86_64/bin/i686-linux-android-gcc: not found Project ERROR: You need to set the ANDROID_NDK_ROOT environment variable to point to your Android NDK. Could not read qmake configuration file /home/mbnoimi/.Qt5.2.1/5.2.1/android_x86/mkspecs/android-g++/qmake.conf. /bin/sh: 1: /opt/android/ndk/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin/arm-linux-androideabi-gcc: not found Project ERROR: You need to set the ANDROID_NDK_ROOT environment variable to point to your Android NDK. Could not read qmake configuration file /home/mbnoimi/.Qt5.2.1/5.2.1/android_armv7/mkspecs/android-g++/qmake.conf.
P.S. I asked about issue in the Forums but unfortunately I didn't get any response so I felt desperate and decided to file it as a bug