On Sunday, 29 July 2018 12:18:38 PDT BogDan Vatra via Development wrote:
> For 5.11 we used 10e and I'm afraid we can't afford to change it without
> proper testing.
Thanks.
Someone can fix the issue then. I recommend
#ifdef Q_OS_ANDROID
// Android libc told us for 7 years to use a file Android
For 5.11 we used 10e and I'm afraid we can't afford to change it without proper
testing.
Cheers,
BogDan.
On July 29, 2018 10:11:53 PM GMT+03:00, Thiago Macieira
wrote:
>On Sunday, 29 July 2018 11:15:38 PDT BogDan Vatra via Development
>wrote:
>> AFIK qt 5.12 will use ndk r16 or better.
>
>The
On Sunday, 29 July 2018 11:15:38 PDT BogDan Vatra via Development wrote:
> AFIK qt 5.12 will use ndk r16 or better.
The question was for Qt 5.11 using fixed headers.
The fix in Bionic happened in January 2015.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
AFIK qt 5.12 will use ndk r16 or better.
On July 29, 2018 6:16:30 PM GMT+03:00, Thiago Macieira
wrote:
>On Monday, 16 July 2018 08:50:05 PDT Thiago Macieira wrote:
>> On Monday, 16 July 2018 00:08:44 PDT Bogdan Vatra via Development
>wrote:
>> > The clang support was added and works fine from
On Monday, 16 July 2018 08:50:05 PDT Thiago Macieira wrote:
> On Monday, 16 July 2018 00:08:44 PDT Bogdan Vatra via Development wrote:
> > The clang support was added and works fine from 5.9. But I think is too
> > late to switch NDK for 5.11.
>
> I'm not asking to change compilers. I am asking
On Monday, 16 July 2018 00:08:44 PDT Bogdan Vatra via Development wrote:
> The clang support was added and works fine from 5.9. But I think is too late
> to switch NDK for 5.11.
I'm not asking to change compilers. I am asking whether we can require fixed
NDK headers?
--
Thiago Macieira -
În ziua de vineri, 13 iulie 2018, la 23:50:36 EEST, Thiago Macieira a scris:
> On Wednesday, 11 July 2018 23:32:16 PDT Thiago Macieira wrote:
> > On Wednesday, 11 July 2018 23:00:50 PDT Liang Qi wrote:
> > > https://bugreports.qt.io/browse/QTQAINFRA-1681
> > >
On Wednesday, 11 July 2018 23:32:16 PDT Thiago Macieira wrote:
> On Wednesday, 11 July 2018 23:00:50 PDT Liang Qi wrote:
> > https://bugreports.qt.io/browse/QTQAINFRA-1681
> > https://codereview.qt-project.org/#/c/216306/
> > https://codereview.qt-project.org/#/c/229465/
> >
> > People are
On Wednesday, 11 July 2018 23:00:50 PDT Liang Qi wrote:
> https://bugreports.qt.io/browse/QTQAINFRA-1681
> https://codereview.qt-project.org/#/c/216306/
> https://codereview.qt-project.org/#/c/229465/
>
> People are working on that, hope will get update after summer vacations.
Thank you. Do I
https://bugreports.qt.io/browse/QTQAINFRA-1681
https://codereview.qt-project.org/#/c/216306/
https://codereview.qt-project.org/#/c/229465/
People are working on that, hope will get update after summer vacations.
-- Liang
On Fri, 6 Jul 2018 at 03:54, Thiago Macieira
wrote:
> I've just been
] On
Behalf Of Vincas Dargis
Sent: Thursday, July 05, 2018 3:29 PM
To: Thiago Macieira ; development@qt-project.org
Subject: Re: [Development] Raising the minimum Android NDK version
On 7/5/18 10:54 PM, Thiago Macieira wrote:
> Instead of applying a workaround, can we just raise the minimum NDK to
&g
On 7/5/18 10:54 PM, Thiago Macieira wrote:
Instead of applying a workaround, can we just raise the minimum NDK to one
that fixes the issue? Are there still valid reasons for requiring old NDKs?
I see that there is still work in progress to support Clang, as GCC NDK is being deprecated, if I
12 matches
Mail list logo
