Re: using a non standard openssl
Re: using a non standard openssl
- Subject: Re: using a non standard openssl
- From: Rich Collyer <email@hidden>
- Date: Wed, 1 Oct 2008 17:56:06 -0700
Something is still wrong. Is there a verbose mode for the linker?
+++++++++++++++++++++++
Rich Collyer
Senior Software Engineer
IronKey, Inc.
email@hidden
+++++++++++++++++++++++
On Oct 1, 2008, at 2:11 PM, Robert Allen wrote:
Rich:
You need to use linker flag -search_paths_first to tell the linker to
use static libraries that occur earlier in the link path rather than
scanning the whole link path for dylibs then coming back to look
through
it again for static libs.
-Robert
------------------------------------------------------------------------
--
"If ignorance is bliss, why aren't more people happy?"
------------------------------
-----Original Message-----
From: xcode-users-bounces+rallen=email@hidden
[mailto:xcode-users-bounces+rallen=email@hidden]
On Behalf Of Rich Collyer
Sent: Wednesday, October 01, 2008 4:47 PM
To: email@hidden
Subject: using a non standard openssl
I need to be able to build and link to a non-standard version
of openssl (that contains my own engine). However, when I
build the application that calls openssl, it does not appear
to call my version. I am guessing that it is calling the
standard one that is included in the OS (/usr/bin/libcrypto.dylib).
I have tried to use the -dylib_file option, but that didn't
seem to work either.
I am also building it as a static lib verses a dynamic lib.
Any thoughts?
+++++++++++++++++++++++
Rich Collyer
Senior Software Engineer
email@hidden
+++++++++++++++++++++++
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