Re: Header Files Copied into App Bundle - Why?

FROM : David Emme
DATE : Tue Jul 18 22:09:00 2006

[ Sorry about starting this thread on the wrong list...  -Dave ]


On Jul 18, 2006, at 12:32 PM, Chris Hanson wrote:

> On Jul 18, 2006, at 10:40 AM, David Emme wrote:
>

>> Why is it copying the .h files into the app bundle?

>
> It's copying them because you're making them a member of the target 
> that produces your application, but there is no Copy Headers build 
> phase in the target.  The fact that there's no such build phase in 
> the target is by design; this build phase is only intended to be 
> used when creating frameworks, and header files don't need to be 
> members of a target just because they're in a project.
>
> If you do make a header file a member of a target, it will be 
> routed to the most appropriate available build phase; without a 
> Copy Headers build phase, it will be be routed to the target's Copy 
> Bundle Resources build phase.
>
> What version of Xcode are you using?


Xcode 2.3

I originally had a "Core Data Document-based Application" project. I 
decided to add a Spotlight importer, so I created a new "... with 
Spotlight Importer" project and moved my original source files into 
it. As far as I can tell, the "Copy Files" step that was copying the 
headers as well as the importer bundle was set up for me automagically.


On Jul 18, 2006, at 11:18 AM, Nick Zitzmann wrote:

> There's a bug in Xcode where, if you have a copy files build phase 
> but not a headers build phase, then any headers you check get added 
> to the copy files phase, which is probably not what you want.


I removed all of the header files from the "Copy Files" step, and 
added a "Copy Headers" step to the beginning of my build sequence. 
This seems to have solved the problem, at least for now.

-Dave
--
Weiler's Law:
Nothing is impossible for the man who doesn't have to do it himself.