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: "James W. Walker" <email@hidden>
- Date: Wed, 2 Aug 2006 08:42:06 -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.
Now, that's news to me. Of course, if I choose "New File..." to
create a C++ source and header, Xcode adds both to the project.
Maybe that's what gave me the impression that headers were supposed
to be in the project.
No, wait, here's where I got the impression that the headers were
supposed to be in the project. In "Porting CodeWarrior Projects to
Xcode", it says "Xcode also supports recursive search paths; however,
it is generally recommended that your project include explicit
references to its header files. For example, when you add a .c file
to your Xcode project, you don’t typically add a search path for the
associated header file. Instead, you drag the actual header file into
a group in the Groups & Files list in the project to add a reference
to the header." _______________________________________________
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