Hi Rush,
Your solution has been very helpful.
> (2) does the correct thing. It statically links against your version of
> libssl.a. It also acts just like it found the library because of a -lssl
> on the linker command line. (Only the functions that are required are
> pulled into your executable,
Thank you Joseph, I also wondered to see ssl libraries in /usr/lib on
my machine, when I started using ssl, but before seeing them there I
had tried to compile Openssl on my machine so I thought this
compilation has placed them there.
But still, client says link them statically :(
Regards,
--
Qad
Hi Rush,
Thank you very much for your detailed answer, I'll try this solution.
Regards,
--
Qadeer
On 4/27/05, Rush Manbert <[EMAIL PROTECTED]> wrote:
> Hi Qadeer,
>
> I believe you can just statically link the openssl libraries while
> creating a dynamic library. Your dynamic library will just
Hi Qadeer,
I believe you can just statically link the openssl libraries while
creating a dynamic library. Your dynamic library will just be bigger
than it would be otherwise. The libraries that are named *.a are the
static versions. Everything I'm about to say applies to the GNU tool set
on Mac
org
Subject: How to link statically openssl in a dylib
Hi,
I am using openssl in an application (this application actually is a
".dylib" on Mac OSX).
Currently I am linking openssl calls by using "-lssl -lcrypto" linker
options. Since this links openssl calls dynamcally th
Hi,
I am using openssl in an application (this application actually is a
".dylib" on Mac OSX).
Currently I am linking openssl calls by using "-lssl -lcrypto" linker
options. Since this links openssl calls dynamcally therefor I can only
use resulting application on the computers where "libssl.dylib
