Accessing static library built into framework
Accessing static library built into framework
- Subject: Accessing static library built into framework
- From: Brent Gulanowski <email@hidden>
- Date: Thu, 21 Oct 2004 18:18:29 -0400
Could use some help with this.
I have application and a framework, both of which use parts of a
static library. By necessity I was linking both the app and the
framework to the lib, but I'm getting an error which makes me suspect
that is not a good idea. (That it probably shouldn't happen for
another reason is not enough to dissuade me completely.)
The problem will go away as soon as encapsulate all the static lib's
functionality in the framework, which is my goal, but I'm not quite
there yet.
So can I expose functions from the static lib through the (embedded
Cocoa) framework so that I don't have to link the main application to
the library? If I like the app to a dynamic version of the library,
will that work, or will I just have the library loaded twice (once
statically in the framework, once dynamically for the app)?
Is two levels of indirection just too much for the linker to resolve?
--
Brent Gulanowski
http://www.boredastronaut.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden