Avoiding link conflicts with a static library
Avoiding link conflicts with a static library
- Subject: Avoiding link conflicts with a static library
- From: Redler Eyal <email@hidden>
- Date: Wed, 04 Apr 2018 19:25:33 +0300
Hi All,
We're developing an SDK for iOS, the SDK is delivered in a statically-linked
framework. Our library uses openCV and we link OpenCV into the delivered
framework binary.
This SDK was deployed successfully with some clients but we're having an issue
with one client whose application also links indirectly (via card-io) with
openCV. The version of openCV they're using is different then then one we use
and as a result of this conflict, the application crashes upon use of our SDK.
We are aware that the following are possible solutions to the problem:
a. Switch to use the same version of OpenCV as our client.
b. Build our framework as a dynamic library (where we a supposed to be able to
hide openCV inside)
Both of these options are not optimal for us and we trying to see if we have
any other option.
One direction that seems to make sense is to pre-link openCV with our
framework. I tried doing that setting the "Perform Single-Object Prelink" to
YES and added openCV in the "Prelink libraries" setting. That builds OK but
when we actually try to link with our SDK, the linker seems to complain about
the openCV symbols as missing.
My Questions:
a. Is there any other solution beside what I've mentioned above?
b. Does the pre link concept make sense as a solution?
c. If b is true, any idea what I could be doing wrong setting up this pre-link?
Any thoughts or ideas on the matter would be much appreciated.
Thanks,
Eyal Redler
------------------------------------------------------------------------------------------------
"If Uri Geller bends spoons with divine powers, then he's doing it the hard
way."
--James Randi
www.eyalredler.com
_______________________________________________
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