Re: [Xcode-users] Turning "may not respond to" warnings into errors?
Re: [Xcode-users] Turning "may not respond to" warnings into errors?
- Subject: Re: [Xcode-users] Turning "may not respond to" warnings into errors?
- From: Alexander von Below <email@hidden>
- Date: Thu, 22 Nov 2007 13:10:03 +0100
| Yes, I do not want the build to succeed if the warning is encountered, and I want to know where it was encountered quickly.
Other warnings can be promoted using -Werror=, so I was wondering if there was some keyword I could use for this Warning
Alex
Am 21.11.2007 um 16:01 schrieb Eric Slosser: On 21/11/2007, at 7:18 AM, Alexander von Below wrote:
recently, there had been the question about how to make "may not respond to ... " warnings.
I want the opposite thing: I want them to be hard errors.
There is wizzardry in gcc to do that, but my searching powers have failed me. If anyone could point me in the right direction, that would be great.
What are you really trying to do? Stop the build if that warning is emitted? If so, would it be acceptable to post-process the output of the compilation with a script that would signal a failure if it finds the warning?
|
_______________________________________________
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