Re: Linking a static (.a) library into a framework
Re: Linking a static (.a) library into a framework
- Subject: Re: Linking a static (.a) library into a framework
- From: Mike Laster <email@hidden>
- Date: Sat, 30 Oct 2004 20:19:39 -0400
On Oct 29, 2004, at 6:35 PM, Eric Albert wrote:
I'm going down the road of using the .dylib now but it isn't working
correctly either.
For some reason, the linker isn't setting the full path to the .dylib
file
and higher-level frameworks that link against Spread.framework fail
because they cannot find libspread.dylib:
otool -Lv Spread
Spread:
/Marketocracy/Frameworks/Spread.framework/Versions/A/Spread
(compatibility version 1.0.0, current version 1.0.0)
time stamp 1099084681 Fri Oct 29 17:18:01 2004
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
(compatibility version 300.0.0, current version 500.56.0)
time stamp 1095214563 Tue Sep 14 22:16:03 2004
libspread.1.0.dylib (compatibility version 0.0.0, current
version 0.0.0)
time stamp 1098987191 Thu Oct 28 14:13:11 2004
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 71.1.1)
time stamp 1092508094 Sat Aug 14 14:28:14 2004
Every other library has a fully qualified path, but for some reason
libspread.1.0.dylib does not.
Sounds like libspread wasn't linked with an install name. Give it an
install name that corresponds to its location in the file system and
things should work.
Yes, that is exactly what it was. I patched the makefile and sent the
fix back to the maintainers.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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