Re: (objc_warning) is valid for ObjC/ObjC++ but not for C
Re: (objc_warning) is valid for ObjC/ObjC++ but not for C
- Subject: Re: (objc_warning) is valid for ObjC/ObjC++ but not for C
- From: "Sean McBride" <email@hidden>
- Date: Mon, 12 May 2008 17:59:42 -0400
- Organization: Rogue Research
On 5/12/08 2:33 PM, Roy Lovejoy said:
>In an XCode project's build settings, I can't seem to find where to
>put ObjC ONLY warnings, such as strict-selector-match & undeclared-
>selector, -such-that- I do NOT get "warning: command line option "-
>Wstrict-selector-match" is valid for ObjC/ObjC++ but not for C"
>warnings.
>
>My project is shortly going to have 'warnings are errors' flipped on
>(as all good projects should), but I don't want to -cut-back- on the
>warnings to make it under this bar, especially the ObjC warnings.
>
>GCC 4.0's "Other C Flags" -seemed- to be the place, but I get the
>above warning..
>"Other Warning Flags" is worse, as it then gets the same warning-
>warning, with the additional "but not for C++" tag.
You're not missing anything, there's no good way to deal with this.
(<rdar://5295989 for Apple folk.) One option is to specify warning
flags per file, but that's very annoying.
--
____________________________________________________________
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