Re: Xcode - An Apple Embarrassment NOT
Re: Xcode - An Apple Embarrassment NOT
- Subject: Re: Xcode - An Apple Embarrassment NOT
- From: Warren Dodge <email@hidden>
- Date: Tue, 06 Mar 2012 08:23:41 -0800
On Mar 6, 2012, at 1:42 AM, Andreas Grosam wrote:
>
> On Mar 6, 2012, at 7:54 AM, Joar Wingfors wrote:
>
>>
>>> Could this explain why Issue Navigator is no longer taking me to the source line of code for issues?
>>
>>
>> Not sure, but I wouldn't think so. If Xcode has found an issue in your project, it should per definition have enough information to take you to that issue. If you can reproduce a problem of that nature, please file a bug report.
>
>
> I have been able to reproduce such an issue. It's caused by a build setting which is a relative path definition containing a "..", e.g.:
> MY_INCLUDE_PATH= ../Source/include
> used for a header search path.
>
> Xcode incorrectly prepends the path with a "/" when inserting the issue in the list, e.g.
>
> /../Source/include/offending_file.h
>
>
> it should be:
> ../Source/include/offending_file.h
>
> or, respectively, with an absolute path, e.g.:
> /Users/me/MyDevelop/MyProject/Source/include/offending_file.h
>
> You can find this out when copying & pasting the issue into a text editor.
>
> Note: clang's transcripts are correct.
>
>
> Regards
> Andreas
You can usually work around this issue by starting the relative path with an Xcode build variable such as $SRCROOT.
So, MY_INCLUDE_PATH= ../Source/include
might become
MY_INCLUDE_PATH= $SRCROOT/../Source/include
Warren
_______________________________________________
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