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: Aroon Pahwa <email@hidden>
- Date: Wed, 25 Mar 2009 11:51:49 -0700
- Acceptlanguage: en-US
- Thread-topic: Export headers with static library on build?
On 3/25/09 7:51 AM, "Joar Wingfors" <email@hidden> wrote:
>
>
> On 24 mar 2009, at 17.35, Aroon Pahwa wrote:
>
>> First, what does the OCopy 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.
>
I did a little more homework last night and figured out what the Copy
Headers build phase does and what you're saying sounds accurate. In
particular, it copies the specified headers to the appropriate output
directory based on their Role (public, private, project).
What struck me as odd is that the default output directory for public
headers is /usr/local/include which, to me, would be similar to the binary
output directory being /usr/local/bin.
Is there a good reason for the output directory being /usr/local/include? I
want it to be something more like build/Debug/Headers/ so I can zip up the
build/Debug folder and have the binary and the headers packaged and ready to
distribute. Making that change is simple enough so I don't think I need help
with that but...
I don't understand why everyone wouldn't want what I want...so I must be
missing something. Can anyone tell me what it is? Any reason I really
wouldn't want to change the output directory?
Thanks!
Aroon
_______________________________________________
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