On 08/03/16 09:04, Nurmi J-P wrote:
On 07 Mar 2016, at 20:45, Gunnar Sletta wrote:
I would like to suggest Robin Burchell for the role of future Qt
Quick maintainer.
He is a long time Qt contributor and has repeatedly shown insight
and dedication to the project. From
> On 07 Mar 2016, at 20:45, Gunnar Sletta wrote:
>
> I would like to suggest Robin Burchell for the role of future Qt Quick
> maintainer.
>
> He is a long time Qt contributor and has repeatedly shown insight and
> dedication to the project. From various work he has solid
Mitch asked:
>> Is this worth mentioning in the documentation?
Andre' P replied:
> I think it would make sense to list the features that are affected so
> that users can decide whether they actually need one of them, or not,
> instead of having this unspecific (and untrue) "strange things may
>
Hello everyone,
I would like to point out that QNX is unable to build the 5.7 branch. The
commit that probably triggered the breakage is:
d6bb01e1779f1840dfbab57c6ecd615587bbde62
Force inclusion of on QNX systems.
This raises my first question: should this not have been reported by
Hi,
When building Qt 5.7 for QNX a special patch is applied in the CI that fixes
the Dinkumware headers. You were CCed when this was discussed (Subject was
"QNX and Dinkumware support for constexpr and nullptr").
Simon
Original Message
From: Rafael Roquetto
Sent: Tuesday, March 8, 2016
Hi Simon,
You are right, I completely forgot about that thread. Thanks for the feedback.
Cheers,
Rafael
On Tue, Mar 08, 2016 at 06:31:15PM +, Hausmann Simon wrote:
> Hi,
>
> When building Qt 5.7 for QNX a special patch is applied in the CI that fixes
> the Dinkumware headers. You were
No worries :). The fact that you didn't see a proper configure error message
suggests that the follow up patch to verify the qnx installation didn't make it
or is buggy. Hmm.
Simon
Original Message
From: Rafael Roquetto
Sent: Tuesday, March 8, 2016 19:48
To: Hausmann Simon
Cc:
On terça-feira, 8 de março de 2016 18:59:51 PST Hausmann Simon wrote:
> No worries :). The fact that you didn't see a proper configure error message
> suggests that the follow up patch to verify the qnx installation didn't
> make it or is buggy. Hmm.
Indeed, it's change