On Friday 22 May 2015 15:49:42 Jason H wrote:
> I'm not. Qmake is. I don't have those options anywhere in my .pro
The point is that you did something to cause it. Those flags are enabled with
the conditional:
equals(ANDROID_TARGET_ARCH, armeabi-v7a):
ANDROID_TARGET_ARCH is set either in your .p
I'm not. Qmake is. I don't have those options anywhere in my .pro
> Sent: Thursday, May 21, 2015 at 4:00 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] aarch64-linux-android-g++: error: unrecognized
> command line optio
On Thursday 21 May 2015 19:57:59 Jason H wrote:
> /opt/android-ndk-r10d/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x8
> 6_64/bin/aarch64-linux-android-g++
> aarch64-linux-android-g++: error: unrecognized command line option '-mfloat-
> abi=softfp'
> aarch64-linux-android-g++: error: unr
Looks like I have a messy Kit configuration. I'm not sure why Qt is applying
the wrong parameters though.
> Sent: Thursday, May 21, 2015 at 1:57 PM
> From: "Jason H"
> To: "interest@qt-project.org"
> Subject: [Interest] aarch64-linux-android-g++: error
I started prepparing a minimal example for an issue, and I started getting
errors. I've never had a problem and I haven't updated anything in the NDK
/opt/android-ndk-r10d/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-g++
-c -Wno-psabi -march=armv7-a -mfloa
