| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
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.
I have several projects that have headers only locatable via header search path without the headers themselves in the project.
Can you be more specific on when you are seeing this issue?
-Shawn _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xcode-users/email@hidden
| References: | |
| >Re: stop new header from being added to copy files? (From: Nick Zitzmann <email@hidden>) | |
| >Re: stop new header from being added to copy files? (From: Chris Espinosa <email@hidden>) | |
| >Re: stop new header from being added to copy files? (From: Ladd Van Tol <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.