[Development] Clarification on Mac 10.6 support for Qt 5.2
Jani.Heikkinen at digia.com
Fri Jun 7 11:03:25 CEST 2013
>The problem is that the revert needs investigation. I'm not sure that
>reverting this commit alone is enough or won't break other things out there.
For me this sounds quite risky move. Is it really so that we have to do this for Qt5.1 and even Qt5.1 RC1? Or is it possible to make Qt5.1.0 with this and solve this in Qt5.1.1?
From: development-bounces+jani.heikkinen=digia.com at qt-project.org [mailto:development-bounces+jani.heikkinen=digia.com at qt-project.org] On Behalf Of Thiago Macieira
Sent: 6. kesäkuuta 2013 18:16
To: development at qt-project.org
Subject: Re: [Development] Clarification on Mac 10.6 support for Qt 5.2
On quinta-feira, 6 de junho de 2013 11.22.28, Koehne Kai wrote:
> > That means we need to change the Qt 5.1 RC1 build scripts to pass
> > -no-c++11.
> Isn't the lower risk approach to just revert the change in the release
> branch? That is, we'd have the same behavior as with 5.0. I understand that
> passing -no-c++11 explicitly would be more invasive.
To be honest, it might be. Liang found an issue yesterday when compiling
QtLocation, since it has a .pro file with CONFIG -= qt.
The problem is that the revert needs investigation. I'm not sure that
reverting this commit alone is enough or won't break other things out there.
Passing -no-c++11 should be easy. But it doesn't fix Liang's problem.
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development