Re: Source trees & include paths
Re: Source trees & include paths
- Subject: Re: Source trees & include paths
- From: Martin-Gilles Lavoie <email@hidden>
- Date: Tue, 27 Jan 2004 20:31:16 -0500
Le 04-01-26, ` 23:28, David Catmull a icrit :
On Jan 26, 2004, at 7:34 PM, email@hidden wrote:
In Xcode the best way to handle this is to add the desired headers to
the target in question, then Xcode tracks the locations of the headers
via a headermap (where the headername is mapped to a specific file
location).
As I noted previously, I have not had success with this. In general I
have found XCode to be seemingly inconsistent about when adding a
header to the project is needed in order for things to work right. I
filed a bug about my particular situation, #3540721.
Wich seems to be my case as well.
I did have to enter a number of painful paths in the project's Header
Search Path variable (boy is that interface annoying as compared to
CW's Access Path panel). Though, many other include paths seem to be
implicit from the included sources directories.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Martin-Gilles Lavoie
email@hidden
This e-mail certified virus-free (made on Macintosh!)
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.