Fri, Feb 23
there's a new revision of D10757 that shouldn't need this at all.
I've never seen these so I'm surprised. Good that you figured it out though :)
Might be an idea indeed to switch to default language instead of system one. Can you tell at which point the system one is estimated, and based on what?
I'm guessing that QLocale::default defaults to QLocale::system?
Thu, Feb 22
Mon, Feb 19
(btw what I did earlier this week was to introduce ANDROID_COMPILER_PREFIX in the first place, also for an x86 build...)
True I've been editing the toolchain file too, probably for the same reason...
Sun, Feb 18
Sat, Feb 17
Interesting, @dfaure, does setting a different ABI/compiler via the command line actually work for you? Here the command-line parameters are not propagated to compiler runs for configure checks, so they run with the defaults from the toolchain file, which fails at best and ends up with a bizarre ABI mix at worst. I need to edit the corresponding fields in the toolchain file to make this work, no idea how to fix that properly yet.
@dfaure was looking into this as well earlier this week, he may have feedback.
Mon, Feb 12
Fri, Feb 9
Thu, Feb 1
-Wzero-as-null-pointer-constant does exist here, you're right the other one doesn't
Wed, Jan 31
Want me to fix FindQtWaylandScanner.cmake in the same way?
Use ECMQueryQmake.cmake as suggested.
Mon, Jan 29
These flags are not in the Clang warnings (list for each version here: https://github.com/Barro/compiler-warnings)
Sun, Jan 28
+1, but someone else must approve.
Thanks for your review.