Apple

-lcrypto

Does anyone know where this comes from, what it means, how to get rid of it?

The -search_paths_first and tech note 1393 do not seem to have helped.

I have tried the dylib_file option as well, but with no luck.

any other hints?

+++++++++++++++++++++++

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
+++++++++++++++++++++++

References:
	>RE: using a non standard openssl (From: "Robert Allen" <email@hidden>)