Re: stop new header from being added to copy files?
Re: stop new header from being added to copy files?
- Subject: Re: stop new header from being added to copy files?
- From: Ladd Van Tol <email@hidden>
- Date: Wed, 2 Aug 2006 10:06:48 -0700
On Aug 1, 2006, at 9:05 PM, Chris Espinosa wrote:
Your headers do not need to be in your target unless you want them
processed somehow at build time. Your sources can find your
headers just fine, and Find in Project, Class Browser, indexing,
etc. will all work if the headers are simply #included by target
sources and/or are in the project—they don't have to be in the target.
That should be "AND are in the project". None of those features ever
appear to work if the header is located via a header search path, and
is #included by source in the project. This is a somewhat annoying
shortcoming that comes up a lot when we are porting projects from
CodeWarrior for our clients.
Generally it's less of an issue on new projects, because you just add
the appropriate headers to start with.
- Ladd
_______________________________________________
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