Re: Why does xcode flag script output lines as errors?
Re: Why does xcode flag script output lines as errors?
- Subject: Re: Why does xcode flag script output lines as errors?
- From: Greg Hurrell <email@hidden>
- Date: Wed, 26 Apr 2006 01:20:50 +0200
El 26/04/2006, a las 0:15, Marc Epard escribió:
What does xcode look for?
How can I prevent lines from being flagged as errors?
On the other hand, how can I make sure a unit test failure
indication is
flagged as an error?
Inspection of the build results window leads me to believe that
anything with consecutive colons will be flagged as an error:
::
Xcode is actually looking for lines like the following (where "path"
is the full path to the file and "line" is the line number):
path:line: error: description
path:line: warning: description
Clearly, the line with "error:" shows up as an error and the one
marked as "warning:" shows up as a warning. Evidently the parsing is
quite loose, so even if "path" and "line" are empty strings (thus
giving you a double colon, "::") the log entry will show up as an
error/warning (so loose in fact that even if they are not at the
beginning of the line, by the looks of the output that you posted in
your email).
Best wishes,
Greg
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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