On Tue, 8 Aug 2000, Domenico Andreoli wrote:

> i miss the point. dynamic libcurl is linked statically against static
> openssl, if openssl is leaved alone with default settings, right?

No. The linking (static or dynamic) of the two ssl libs and the single
libcurl is done on curl. libcurl is just a lib, it does not link anything by
itself. Thus, when built to use SSL 'curl' requires (at least) three
different libs:

 1. libcurl
 2. libssl
 3. libcrypto

It requires libc and possibly other system-specific libs too.

When 'curl' is linked with:

 1. static SSL libs and dynamic SSL-enabled libcurl it works.
 2. static SSL lib and a SSL-*disabled* dynamic libcurl, it'll work but you
    won't be able to do HTTPS

If you have static SSL libs in your system, although 'curl' is not linked
with them on build time, you won't be able to use HTTPS even if libcurl was
compiled SSL-enabled (it'll give you run-time errors).

If all of these libs are dynamic and present. libcurl's SSL-status will
control wheather the SSL libs are used or not and if HTTPS will work or not.

> please be clear and easy in your explanation, i'm not a great coder and i
> have no shared library experience at all, so i don't know *many* things.

I hope I did clear some of the mist!

> btw, i think that openssl package for debian installs dynamic libraries.
> how can i do to understand if it install static too?

The dynamic/shared ones (normally) use .so extensions while the static ones
use .a.

-- 
      Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol