Re: [Development] Time to switch to android-clang

2018-01-09 Thread Sergio Martins
On 2017-12-19 16:18, Thiago Macieira wrote: On terça-feira, 19 de dezembro de 2017 03:25:17 PST Sergio Martins wrote: Furthermore, supporting both android and android-clang is a maintenance burden: the mkspecs are often broken, either because of a new Qt version or because of a new NDK version.

Re: [Development] Time to switch to android-clang

2017-12-20 Thread BogDan Vatra
On marți, 19 decembrie 2017 11:25:17 EET Sergio Martins wrote: [...] > > The problem of clang generating bigger binaries was much improved with > -Oz, now size increase is only 10%. > Which, on ARM, usually means the bins are slower ;-) [...] Anyway, a +0.5 also from my side. Cheers, BogDan. _

Re: [Development] Time to switch to android-clang

2017-12-19 Thread Thiago Macieira
On terça-feira, 19 de dezembro de 2017 03:25:17 PST Sergio Martins wrote: > Furthermore, supporting both android and android-clang is a maintenance > burden: the mkspecs are often broken, either because of a new Qt version > or because of a new NDK version. Then you have to test not only gcc and >

[Development] Time to switch to android-clang

2017-12-19 Thread Sergio Martins
Hi all, We need to start offering pre-built android binaries built with android-clang and bump our minimum supported NDK version. gcc on android is pretty much dead since 2016: "GCC is no longer supported. It will be removed in NDK r18. libc++ is now the default STL for CMake and standalone