[Development] Clarification on Mac 10.6 support for Qt 5.2
Eike.Ziller at digia.com
Tue Jun 11 11:26:23 CEST 2013
On 07.06.2013, at 18:50, Olivier Goffart <olivier at woboq.com> wrote:
> On Friday 07 June 2013 10:22:56 Koehne Kai wrote:
>> My suggestion:
>> - Leave Qt 5.1.0 as it is right now, move on with the release process
>> - Investigate providing an additional binary installer with Qt compiled
>> 10.6 (e.g. with 5.1.1) - Thoroughly document the problem for people
>> compiling their own Qt
> But what about the binary compatibility break?
> Since libstdc++ and libc++ are not binary compatible, if one use third party
> library that uses the standard library, his application will no longer work
> unless that 3rd party library is also re-compiled against the same standard
> Is it not an important issue?
When I build Qt 5.1 in the current standard configuration (e.g. with c++11 and therefore with libc++)
I still get QtScript and QtWebKit built against libstdc++ and with deployment target 10.6, even though the rest of Qt is built against libc++ and with deployment target 10.7. Because they do CONFIG -= c++11 .
This will also happen for any other project / library etc that explicitly doesn't want c++11.
The deployment target thing is probably a lesser annoyance though it still is ugly, especially for QtWebKit and QtScript which are *part* of Qt and should therefore build with the same configuration.
But does anyone know about the consequences of mixing libc++ and libstdc++ ?
> Woboq - Qt services and support - http://woboq.com - http://code.woboq.org
> Development mailing list
> Development at qt-project.org
Eike Ziller, Senior Software Engineer - Digia, Qt
Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
More information about the Development