Re: Avoiding link conflicts with a static library
Re: Avoiding link conflicts with a static library
- Subject: Re: Avoiding link conflicts with a static library
- From: Alex Zavatone <email@hidden>
- Date: Thu, 05 Apr 2018 15:51:49 -0500
> On Apr 5, 2018, at 3:05 PM, Jim Adams <email@hidden> wrote:
>
> We build ours using archive before lipo-ing and we don’t have to strip the
> simulator bits out.
My point was that when you distribute to clients, they will want to test using
a simulator, but will want to ship without it. So, you’ll likely need to
distribute more than one binary.
If a crash is discovered in your framework by the client or by the client’s
clients, they are going to want to have simulator and debug symbols support to
debug.
Shipping anything out of your company with debug symbols will often be regarded
as a security risk, so there is that to consider regarding your intellectual
property and agreements with the client. That’s for the managers to decide.
This leaves you with the potential for 3 copies of the binary that you may need
to distribute.
I managed this by creating build configs for each and then built or archived
according to what was needed.
- Alex Zavatone
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden