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: Jens Alfke <email@hidden>
- Date: Wed, 04 Apr 2018 14:56:39 -0700
> On Apr 4, 2018, at 12:17 PM, Redler Eyal <email@hidden> wrote:
>
> 1. It makes it easier to pirate our technology (having our stuff neatly
> packaged seperaterly)
> 2. (More importantly) It makes the client's binary larger since it will have
> to include our full library, including simulator code. (correct me if I'm
> wrong)
The simulator code has to be stripped out before submitting an app. The app
developer can add a Run Script build phase with a 'lipo' command to do this.
>> No, you should ask your client to remove the simulator slice before
>> submitting to the App Store.
>
> I guess, but it would hurt the usage simplicity. Certainly compared to the
> current solution as a static library.
Any app using Carthage already has to do this, so it's apparently not a deal
breaker for many developers.
—Jens
_______________________________________________
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