Re: Sending a build message less severe then #warning
Re: Sending a build message less severe then #warning
- Subject: Re: Sending a build message less severe then #warning
- From: Sam Krishna <email@hidden>
- Date: Tue, 26 May 2009 11:26:07 -0400
Couldn't I just build a new gcc codebase post-gcc-4.0.1 and use that?
Wouldn't the patches already be in there?
Live Playfully,
Sam
-----
If he listens in faith,
finding no fault, a man is free
and will attain the cherished words
of those who act in virtue.
On May 25, 2009, at 12:40 PM, Alex Curylo wrote:
On 25-May-09, at 9:19 AM, email@hidden wrote:
Is there a way to send a build message less severe then #warning to
the build panel in such a way that it:
(1) appears in the build output panel (the clickable part) and
(2) does not trip the compiler when I have set
GCC_TREAT_WARNINGS_AS_ERRORS = YES
Well, apparently #pragma message finally got accepted into gcc
http://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Pragmas.html#Diagnostic-Pragmas
but it seems that happened after the 4.0.1 my Xcode is using, I'm
guessing it would have been at rev 138206 as discussed in this thread.
http://gcc.gnu.org/ml/gcc-patches/2008-07/msg02169.html
You could always hunt down the appropriate Apple gcc sources and
patch your own if you *really* want this *right* *now*, I suppose.
--
Alex Curylo -- email@hidden -- http://www.alexcurylo.com/
"Going out with Al is like watching a car wreck."
-- Heather Stewart
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden