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: Wed, 04 Apr 2018 19:53:33 -0500
> On Apr 4, 2018, at 2:38 PM, Saagar Jha <email@hidden> wrote:
>
>
> Saagar Jha
>
> I may be misunderstanding you, but why does your code need to be separate?
> Can’t you statically link against your framework, which dynamically opens
> OpenCV (packaged as a framework)?
>
>> 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)
>
> No, you should ask your client to remove the simulator slice before
> submitting to the App Store.
This is controlled in the build settings for release builds. Compiled
Simulator code is not packaged and should not be packaged in a release build.
_______________________________________________
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