Re: Target's header files added to built product's resources?
Re: Target's header files added to built product's resources?
- Subject: Re: Target's header files added to built product's resources?
- From: Scott Tooker <email@hidden>
- Date: Tue, 3 May 2005 02:34:04 -0700
Yes, the project templates were changed in Xcode 1.5, but the
relevant question at this point is "do you see this bug in Xcode
2.0?". The desired behavior is that created headers do not get added
to a specific target unless the headers are part of the product the
target generates.
Scott
On May 3, 2005, at 2:08 AM, Shaun Wexler wrote:
On May 3, 2005, at 1:31 AM, Scott Tooker wrote:
Actually, unless you are building a product that includes headers
(like a framework) you don't need to add the headers to the target
at all, simply having them in the project is enough. The Copy
Headers build phase is only interesting in the case where the
headers are actually being placed in the built product, otherwise
the build phase is a no-op.
In Xcode 2.0 we no longer auto-route headers to the Build
Resources phase anymore, which should avoid accidentally adding
the headers to the wrong build phase.
The BUG, of course, is that when a new file is created and added to
targets via the dialog checkboxes, the headers are also added, so
if there isn't a Headers phase, they go into Resources and are
subsequently copied into the package (in Xcode 1.5).
AFAIR, default project templates in Xcode 1.2 and earlier always
included Headers phases in each target, as well as newly created
targets. Correct?
--
Shaun Wexler
MacFOH
http://www.macfoh.com
_______________________________________________
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