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: Redler Eyal <email@hidden>
- Date: Thu, 05 Apr 2018 12:19:29 +0300
>>
>>> 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.
My understanding is that the dynamic lib is copied as a resource and not
processed automatically that way.
_______________________________________________
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