You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use this approach to build my own framework, but I need to use some other static libraries (.a) in the framework code and it fails at link stage when building the application project that use this framework. Is there any specific thing I should do with the .a files in the framework in order to them being included in the final .framework file?
Thanks!
The text was updated successfully, but these errors were encountered:
Just guessing, but did the extra .a file get drag dropped correctly into
the App build phase for Link Binaries?
IMO it's a bit of a pain to use Xcode in this way but using the plus button
to add link binaries is even harder since you must navigate your filesystem
for those products.
If not that then -ObjC or -all_load in your App linker flags?
On Jan 14, 2013 6:53 AM, "roisg" notifications@github.com wrote:
I'm trying to use this approach to build my own framework, but I need to
use some other static libraries (.a) in the framework code and it fails at
link stage when building the application project that use this framework.
Is there any specific thing I should do with the .a files in the framework
in order to them being included in the final .framework file?
Thanks!
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/36.
I'm trying to use this approach to build my own framework, but I need to use some other static libraries (.a) in the framework code and it fails at link stage when building the application project that use this framework. Is there any specific thing I should do with the .a files in the framework in order to them being included in the final .framework file?
Thanks!
The text was updated successfully, but these errors were encountered: