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: William H.Schultz <email@hidden>
- Date: Fri, 16 May 2008 08:36:25 -0700
On May 12, 2008, at 3:55 PM, Roy Lovejoy wrote:
On May 12, 2008, at 2:59 PM, Sean McBride wrote:
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.
I'm assuming there's no way to turn this 'warning-warning' off?
(if you can't avoid the warning, squelch it)
What about configuring Xcode to compile every file as if it was Obj-C++? That might be reasonable workaround.
-------------------------------
Hank Schultz
Cedrus Corporation
http://www.cedrus.com/
|
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________
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