Document that PKG_CONFIG_PATH is the preferred way to configure with

OpenSSL.
This commit is contained in:
Dan Fandrich 2008-07-29 20:59:51 +00:00
parent 5dafa4a270
commit 1f3007dbb4

View File

@ -53,8 +53,12 @@ UNIX
./configure --with-ssl ./configure --with-ssl
If you have OpenSSL installed somewhere else (for example, /opt/OpenSSL,) If you have OpenSSL installed somewhere else (for example, /opt/OpenSSL)
you can run configure like this: and you have pkg-config installed, set the pkg-config path first, like this:
env PKG_CONFIG_PATH=/opt/OpenSSL/lib/pkgconfig ./configure --with-ssl
Without pkg-config installed, use this:
./configure --with-ssl=/opt/OpenSSL ./configure --with-ssl=/opt/OpenSSL
@ -70,20 +74,20 @@ UNIX
(with the Bourne shell and its clones): (with the Bourne shell and its clones):
CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \ CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
./configure ./configure
(with csh, tcsh and their clones): (with csh, tcsh and their clones):
env CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \ env CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
./configure ./configure
If you have shared SSL libs installed in a directory where your run-time If you have shared SSL libs installed in a directory where your run-time
linker doesn't find them (which usually causes configure failures), you can linker doesn't find them (which usually causes configure failures), you can
provide the -R option to ld on some operating systems to set a hard-coded provide the -R option to ld on some operating systems to set a hard-coded
path to the run-time linker: path to the run-time linker:
LDFLAGS=-R/usr/local/ssl/lib ./configure --with-ssl env LDFLAGS=-R/usr/local/ssl/lib ./configure --with-ssl
MORE OPTIONS MORE OPTIONS
------------ ------------
@ -128,7 +132,7 @@ UNIX
To build with GnuTLS support instead of OpenSSL for SSL/TLS, note that To build with GnuTLS support instead of OpenSSL for SSL/TLS, note that
you need to use both --without-ssl and --with-gnutls. you need to use both --without-ssl and --with-gnutls.
To build with yassl support instead of OpenSSL or GunTLS, you must build To build with yassl support instead of OpenSSL or GnuTLS, you must build
yassl with its OpenSSL emulation enabled and point to that directory root yassl with its OpenSSL emulation enabled and point to that directory root
with configure --with-ssl. with configure --with-ssl.
@ -148,8 +152,8 @@ UNIX
The Open Watcom C compiler on Linux requires configuring with the variables: The Open Watcom C compiler on Linux requires configuring with the variables:
CC=owcc AR="$WATCOM/binl/wlib" AR_FLAGS=-q RANLIB=/bin/true \ ./configure CC=owcc AR="$WATCOM/binl/wlib" AR_FLAGS=-q \
STRIP="$WATCOM/binl/wstrip" CFLAGS=-Wextra RANLIB=/bin/true STRIP="$WATCOM/binl/wstrip" CFLAGS=-Wextra
Win32 Win32