Re: Linking against libcrypto.dylib fails at strip
Re: Linking against libcrypto.dylib fails at strip
- Subject: Re: Linking against libcrypto.dylib fails at strip
- From: Steve Weller <email@hidden>
- Date: Sat, 10 Feb 2007 15:55:48 -0800
Nick, Thanks. The only reason I tried adding it was because without
it I got unresolved symbols. Now you have directed me to the right
area I found the problem. In case anyone else runs into this:
In order to include linking against libcrypto.dylib I had to add -
lcrypto to the linker flags by clicking on the target, clicking on
Info, and adding -lcrypto to the Other Linker Flags line (under
Linking) for all configurations.
On Feb 10, 2007, at 2:55 PM, Nick Zitzmann wrote:
On Feb 10, 2007, at 3:14 PM, Steve Weller wrote:
I thought I knew how to link against a dynamic library: drag it
into the Linked Frameworks folder in XCode and check Copy so that
it is added to the bundle and is available when deployed. However
strip is failing with "dynamic stub library can't be changed once
created".
I am compiling on an Intel machine for Intel. The dynamic library
is coming from Developer/SDK/MacOSX10.4u.sdk /usr/lib and is
Universal. Is this an architecture problem, a library problem, or
what?
You're trying to copy a stub library instead of a dynamic library.
The libraries found inside an SDK are stubs, not the real libraries.
But you should never have to copy libcrypto into a bundle because
libcrypto version 0.9.7 has come with every version of Mac OS X
since 10.3.0.
Nick Zitzmann
<http://www.chronosnet.com/>
--
Bagelturf Blog http://homepage.mac.com/bagelturf/
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden