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 11:42:32 +0300
>>>> We have two issues with the dynamic framework
>>>> 1. It makes it easier to pirate our technology (having our stuff neatly
>>>> packaged seperaterly)
>>>
>>> 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)?
>>
>> At the moment, we deliver a static framework. This is linked statically to
>> the client's app and delivered inside the main executable to the app store.
>> If we switch to a dynamic library then our library will be a separate
>> component that is delivered as such to the app store. The potential pirate
>> will only have to dig our the library from the application package (and
>> overcome the other protections, of-course)
>
> OK, but is there anything stopping you from having your static library
> dynamically open OpenCV?
Perhaps not but I'm wondering
a. Will it actually solve the issue (the conflict with the clients OpenCV)?
b. Is it possible to package a static framework with a dynamic library in one
package?
_______________________________________________
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