Re: Embedding a Framework
Re: Embedding a Framework
- Subject: Re: Embedding a Framework
- From: Jerry Krinock <email@hidden>
- Date: Thu, 24 Jul 2014 08:50:32 -0700
On 2014 Jul 24, at 08:14, Roland King <email@hidden> wrote:
> name /Library/Frameworks/pcapng.framework/Versions/A/pcapng (offset 24)
> That path in the binary is completely absolute right?
I don’t think so. If I understand you correctly, you are shipping your framework in the Contents/Frameworks/ subdirectory of the application package. I have apps which work the same way. When I otool -l their binaries, I get:
Load command 11
cmd LC_LOAD_DYLIB
cmdsize 96
name @executable_path/../Frameworks/Bkmxwork.framework/Versions/A/Bkmxwork (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 1.0.0
compatibility version 1.0.0
> Is my only option using install_name_tool and changing the name to an @rpath or similar (which is a bit horrid) or is there a way to tell Xcode to embed the Framework in the binary with a binary-relative path when it builds and copies it so the App binary is consistent from the get-go?
In my framework target, Buid Settings, at the “framework” level, I have set Installation Directory to
@executable_path/../Frameworks
and it all works for me.
Here are some old but, I think, still good articles on the subject
http://www.dribin.org/dave/blog/archives/2009/11/15/rpath/
https://mikeash.com/pyblog/friday-qa-2009-11-06-linking-and-install-names.html
_______________________________________________
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