Re: Enabling language-specific warnings in multi-language projects
Re: Enabling language-specific warnings in multi-language projects
- Subject: Re: Enabling language-specific warnings in multi-language projects
- From: "Sean McBride" <email@hidden>
- Date: Fri, 21 Jul 2006 12:41:28 -0400
- Organization: Rogue Research
On 2006-07-20 21:24, Eric Albert said:
>> Urg! How can I get Xcode to use this warning only with languages that
>> support it and not give this silly warning otherwise?
>
>One way to do this is to use "Other C Flags" instead of "Other
>Warning Flags" and then customize "Other C++ Flags" to not contain
>the flag. It's a bit messy, but it worked for me in a quick test.
Thanks for this workaround Eric.
But I don't fully follow... I see that by default OTHER_CPLUSPLUSFLAGS =
$(OTHER_CFLAGS) and so adding -Wdiv-by-zero to OTHER_CFLAGS will of
course apply it to C++ also. This must be what you're referring to when
you say "customize 'Other C++ Flags' to not contain the flag". But how
do I do that? Can I simply set "OTHER_CPLUSPLUSFLAGS = "? Will there
be unintended consequences of OTHER_CPLUSPLUSFLAGS not including the
OTHER_FLAGS as it does by default?
Would you agree though that there needs to be a better way? I ask
because <rdar://4625640> got marked as "Behaves Correctly". No doubt
from gcc's view it is correct behaviour, but from _my_ view (as an
Xcode, not gcc user) I find it quite cumbersome.
Thanks!
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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