Re: Question about dynamic and static libraries
Re: Question about dynamic and static libraries
- Subject: Re: Question about dynamic and static libraries
- From: Bill Northcott <email@hidden>
- Date: Sat, 31 Dec 2005 09:34:09 +1100
On 29/12/2005, at 5:38 PM, Steve Checkoway wrote:
Let's assume that I want to make a framework out of libfoo. I
download, compile, and install it. Then I set up all of the
required directory structure, copy the headers and rename
libfoo.dylib to foo and put it in the correct place. Now all I need
to do is use install_name_tool right? Okay, I need to change the
install name from the following line to the next
/usr/local/lib/libfoo.dylib
@executable_path/../Frameworks/foo.framework/Versions/A/foo
assuming that I want package the framework with my app. Well, I'm
out of luck since the second name is so much longer than the first.
One way or another, I have to hack around this problem.
You are really making your own problem. Why on earth install the
library in /usr/local if that is not the intended install path?
Look at the way Apple do it with open source stuff. They use a
'dst' directory buried in /private/tmp or you home directory. that
way the final install_name path will always be shorter. I have done
this a lot and never had to lengthen a name.
Cheers
Bill
_______________________________________________
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