RE: Treating warnings as errors
RE: Treating warnings as errors
- Subject: RE: Treating warnings as errors
- From: "Jeff Laing" <email@hidden>
- Date: Thu, 26 Mar 2009 19:30:16 -0600
- Thread-topic: Treating warnings as errors
> This works if I create a new project, but in an existing project the
> "GCC 4.0" sections (in one of which "Treat Warnings as Errors"
> resides) are entirely absent. How do I go about getting them back?
Same for me. I've already tried searching for Warning, Error, etc with
no success.
The Compiler stuff only seemed to show if I displayed the info for an
individual .m file and even then I didn't see "Treat Warnings as Errors"
- and that wouldn't be a great solution either - I don't want to have to
tweak each file as I add it to the project.
I've resigned to putting it down to something stupid like "iPhone
projects use a different compiler which doesn't support -Werror" but I
have no basis for saying that - I seriously try not to look under the
covers these days, preferring to be a checkbox/radiobutton user wherever
possible.
Is there a #pragma that can be included to get the same effect? The gcc
info I found on the web suggests that there *isnt* but one can live in
hope that the Internet might be wrong. ;-)
Jeff Laing <email@hidden>
------------------------------------------------------------------------
------
Remember kids, there are no stupid questions, just stupid people.
-- Mr Garrison, "South
Park"
_______________________________________________
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