Re: Export headers with static library on build?
Re: Export headers with static library on build?
- Subject: Re: Export headers with static library on build?
- From: Joar Wingfors <email@hidden>
- Date: Wed, 25 Mar 2009 07:51:27 -0700
On 24 mar 2009, at 17.35, Aroon Pahwa wrote:
First, what does the ‘Copy Headers’ build step mean? I was hoping it
actually copied relevant headers to some output directory where I
could handily zip them up and distribute them along with the binary
but that either isn’t the case or I can’t figure out where it dumps
the headers.
The Copy Headers build phase is not a general purpose and configurable
build phase, AFAIK it's designed with one very specific goal in mind:
To copy header files to the predefined locations in certain bundle
targets - Primarily for frameworks.
You could create your own Copy Headers-like build phase by starting
with a Copy Files build phase, or a Run Script build phase. The
drawback of using a custom build phase is that it will not
automatically track the addition of new header files to your project,
and it will not respect the Public/Private/Project "roles" set on your
header files in the project. That said, making sure that the correct
header files end up in the product is probably something that you'd in
any case want to validate using automated tests.
j o a r
_______________________________________________
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