Errors generated in shell script phase
Errors generated in shell script phase
- Subject: Errors generated in shell script phase
- From: Jonas Maebe <email@hidden>
- Date: Sat, 17 Dec 2005 21:54:39 +0100
Hello,
Since XCode 2.x, error messages generated during a shell script phase
(or in a shell script used as a build rule for a particular source
file) can no longer be double-clicked to jump to the source file. The
reason seems to be that XCode automatically associates such errors
with an imaginary source or project property which does not exist
(e.g. "tool:0") and disregards any file information in the error
line. This worked fine in XCode 1.x.
I've reported this as radar 4343667, but given that this does not
affect any standard XCode projects (it's mainly annoying if you use a
third party compiler which is not supported by XCode), I don't expect
it to be fixed anytime soon. Is there maybe a workaround for that
issue possible?
A sample project which demonstrates the problem (also submitted with
the radar) is available at
http://www.elis.ugent.be/~jmaebe/nobackup/linenr.zip
It's a regular C tool project, whereby I've replaced the rule for
compiling the C file with a script that simply echoes the output that
gcc gives when compiling the (faulty) main file.
Thanks,
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