linking the same static library into two places
linking the same static library into two places
- Subject: linking the same static library into two places
- From: Kenny Leung <email@hidden>
- Date: Thu, 07 Jul 2011 15:58:46 -0700
Hi All.
Hopefully somebody can help me with this:
I have a static library with utilities that I like to use everywhere (it's a static library because we use it on iPhone as well).
So I link it in with a framwork that I'm writing, and also link it in with an application that uses that framework. When I run, I get messages like this:
Class XXXXX is implemented in both <your framework> and <Your app>. One of the two will be used. Which one is undefined.
The same happens with dynamically loaded bundles, etc...
Is there any good way around this? Or just live with the warnings, since I'm pretty sure it doesn't matter which code is used... but then I worry about global variables... are there 2 versions of those?
Thanks!
-Kenny
_______________________________________________
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