So then the request is to change which compiler is used in Mac OS X to build QT 
Creator -- going from an older supported (?still?) compiler to a newer 
supported compiler, right ?

If so, then no objection.
If not, then please clarify.

And a happy new year / Hogswatch Night / what-ever to you and yours

“Sometimes I think the surest sign that intelligent life exists elsewhere in 
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)

----- Original Message -----
From: "Ziller Eike" <[email protected]>
To: "Erik Verbruggen" <[email protected]>, "<[email protected]> 
list" <[email protected]>
Sent: Friday, December 28, 2012 1:59:39 PM
Subject: Re: [Qt-creator] Request: dropping support for macx-g++ to *compile* 
Qt        Creator

Hi,

I don't have a big problem with dropping compilation support of Qt Creator with 
that mkspec/compiler. The "funky incomprehensible error messages" can be 
circumvented by making the Qt Creator .pro file bail out with a useful error + 
hint for that mkspec, similar to how we do it for the Qt version.

Br, Eike

--
Eike Ziller
Senior Software Developer

Digia Germany GmbH
Rudower Chaussee 13, 12489 D-Berlin
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B,
Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius

________________________________________
From: [email protected] 
[[email protected]] on behalf of Erik 
Verbruggen [[email protected]]
Sent: 22 December 2012 14:48
To: <[email protected]> list
Subject: [Qt-creator] Request: dropping support for macx-g++ to *compile* Qt    
Creator

Hi all,

Hereby I would like to ask to officially drop support to *compile* Qt Creator 
with macx-g++.

Please read that again: it is NOT  (¡not! /not/ <blink>not</blink>) *using* Qt 
Creator with macx-g++ (!¡!¡!¡!).

The reason is that the amount of bugs in this >4-years-old compiler is starting 
to seriously freak me out. And yes, I do say this as a full-time mac user, who 
compiles Qt Creator on a more-than-daily basis. It's up to the point that, when 
I hit a compiler error in a file, I manually copy-and-paste the command and 
replace "g++" with "clang++". Especially when using templates, it is just 
getting to be a serious pain in the hinter-parts. A helpful note here might be 
that the only reason for Apple to include this compiler comes down to "you're 
using GCC specific features which we don't know about, or you didn't update 
you're very compiler-sensitive codebase to anything that's not from the 
stone-age or before".

This does have the possibly unfortunate implication that, when using Qt 4.8 
with the default Mac spec, compiling Qt Creator might fail with funky (== 
utterly stupid and erroneous) error messages.

Cheers, and happy Christmas (hacking?),
Erik.
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to