[Development] Clarification on Mac 10.6 support for Qt 5.2

[Thiago Macieira]

On terça-feira, 11 de junho de 2013 09.26.23, Ziller Eike wrote:
> 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.

That's not a problem for API and ABI, since the Qt API and ABI do not expose 
any of the Standard Library. Therefore, no matter which one is used behind the 
scenes for Qt, the user application may still choose.

Deployment, however...

> 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++ ?

See above.

My question is deployment: is there a libc++ on 10.6 for the Qt libraries to 
run against?

If not, we need to turn it off.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130611/76c73f9e/attachment.sig>