Building a framework from a static library
Building a framework from a static library
- Subject: Building a framework from a static library
- From: Jens Alfke <email@hidden>
- Date: Mon, 05 May 2014 10:15:24 -0700
I have a codebase I want to build for OS X both as a static library and as a framework.
I’ve got a static-library target that seems to work fine.
I created a framework target, made it dependent on the library target, and added the library to the link-libraries build phase. There are no source files.
But I can’t get the framework to build properly. First Xcode produced a framework bundle with no dylib in it at all. I tried adding an empty source file to the target, but that produced a dylib with no symbols.
It seems there’s some magic linker flag I need to get the static library’s symbols exported to the dylib, otherwise they all get dead-stripped or something. What do I need to do?
(…Other than a link-map file. That works fine already for the Release config; but for the Debug config I need all the symbols exported, so my unit test bundle can call internal APIs.)
—Jens
_______________________________________________
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