RE: Dependency analysis failing - FIX (Re: What are your top desired improvements in Xcode ?)
RE: Dependency analysis failing - FIX (Re: What are your top desired improvements in Xcode ?)
- Subject: RE: Dependency analysis failing - FIX (Re: What are your top desired improvements in Xcode ?)
- From: Jim Wintermyre <email@hidden>
- Date: Tue, 20 Feb 2007 23:07:03 -0800
> Another reason to add .h files to the project - if you double-
> click the header name in an '#include "MyHeader.h"' in some .c
> file in your project, then select "Open Quickly", XCode will
> fail to find the header if it's only included via a recursive
> header search path (and isn't included directly in the project).
> Radar 5006143.
Yes. But according to this interesting message from Chris Espinosa
on carbon-dev earlier this month, you shouldn't actually need to
add any headers to the project - everything should just work:
: A header does not need to be a project member in order to be
: indexed, searched, or included in a compile; the dependency
: mechanisms and the search paths will cover all included
: headers, whether listed in the project or not.
http://lists.apple.com/archives/xcode-users/2007/Feb/msg00064.html
So it's worth filing bugs in cases where this fails, I suppose.
Indexing/searching is different from "Open Quickly" (apparently).
In the specific case I mentioned (headers included via recursive
search path and not a project member), indexing/searching works but
"Open Quickly" does not.
I spoke too soon; this is also broken for searching (Project Find),
again for the specific case of headers included via a recursive
search path and not included in the project. So indexing is the only
case that actually works. I updated the bug report.
Jim
_______________________________________________
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