Re: Flagging errors from inside a Run Script build phase
Re: Flagging errors from inside a Run Script build phase
- Subject: Re: Flagging errors from inside a Run Script build phase
- From: Jonas Maebe <email@hidden>
- Date: Fri, 27 Jan 2006 10:28:43 +0100
On 27 jan 2006, at 03:35, Dave McCaldon wrote:
If I have a Run Script Build Phase, and my script determines
there's an error, how do I "raise" that to Xcode? There already
seems to be some smarts in Xcode, for example if you add the
following to your script:
rm /tmp/foobar
Assuming the file doesn't exist, this will be flagged as a build
error:
rm: /tmp/foobar: No such file or directory
This is great, I can click on error in the build results and it
takes me to the raw output from the script. However, I just don't
seem to be able to get it to work with my own errors.
I tried the obvious stuff like redirecting my errors to stderr, or
putting keywords such as "ERROR:" in the output, but alas Xcode
doesn't seem to notice it.
Do you exit your script with a non-zero exit code? (e.g. "exit 1") I
do have to admit how exactly XCode determines what is an error and
what isn't is black magic to me as well, and it doesn't seem to be
documented anywhere.
Jonas
_______________________________________________
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