[Interest] Porting to Qt5/macx-xcode Mountain Lion

[Thiago Macieira]

On quarta-feira, 23 de janeiro de 2013 22.08.37, Joshua Grauman wrote:
> Another related question. Is Qt5 going forward always going to use clang 
> for Mac OSX, or should I also expect to see Qt5 prebuilt for gcc on Mac at 
> some point as well?

Forget gcc. Apple stopped updating it at 4.2.3. And their LLVM-backed GCC is 
extremely buggy[*].

The future on Mac goes through Clang. 

Yes, I understand that means losing support for some older versions of Mac OS 
X (definitely 10.5, maybe even 10.6 -- I'm not the expert). That's the only 
reason we're still supporting GCC on Mac at all, because some people still 
need it for older Macs. But we can't keep it up forever.

[*] for example, the assembly code required to detect the CPU features on x86 
simply doesn't compile correctly, so I've turned it off and made Qt always 
report the base CPU features. That means the enhanced draw helpers will be 
built into QtGui but never used. You're carrying dead code if you use GCC 
4.2.3.

-- 
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/interest/attachments/20130124/6bfff849/attachment.sig>