Re: Building an iOS Framework - should its framework/library links be Required or Optional?
Re: Building an iOS Framework - should its framework/library links be Required or Optional?
- Subject: Re: Building an iOS Framework - should its framework/library links be Required or Optional?
- From: Jens Alfke <email@hidden>
- Date: Wed, 04 May 2016 13:00:40 -0700
On May 4, 2016, at 11:03 AM, David Hoerl < email@hidden> wrote:
Subject says it all. My understanding was that for static libraries, the linkage should be "Optional", and the list of required frameworks & libraries made available to adopters of the static library (so they could "Required" link to them.
A static library target doesn’t actually need to list any libraries to link with, because it isn’t linked at all. Instead the compiler output (the .o files) are just collected into an archive. The linking happens when the application (or dynamic library) that uses the static library is built.
—Jens |
_______________________________________________
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