On Tue, 8 Aug 2000, Domenico Andreoli wrote:

> i'm going to make new debian packages based on curl 7.1 and libcurl 7.1
> and what i'd like to know is if all the ssl code is contained in libcurl.

No, curl only contains a few calls to OpenSSL libraries. There's no actual
SSL code anywhere in curl. This code is of course alwys present in libcurl,
although if the configure script doesn't find any SSL, no https:// URLs will
be recognized.

> i made a test. i compiled both curl with ssl enabled and disabled. then i
> called the non-ssl curl with the ssl libcurl in the ld path, it said he
> was working with ssl (i made a curl --version).
>
> does it suffice to switch from non-ssl libcurl to ssl libcurl in order to
> enable ssl support in curl?

There is only one way to truely compile curl *without* SSL and that is to
explicitly call configure like this:

        ./configure --without-ssl

If not, the configure script will check for SSL stuff in the default
places. --enable-ssl is mainly used for telling the configure script where to
look.

Also, make sure you remove the 'config.cache' file between the configure
invokes so that all values are actually re-evaluated and not picked from the
cache.

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