This is what CHANGES (0.9.8g) says about how to build openssl outside
the source tree:
*) Add appropriate support for separate platform-dependent build
directories. The recommended way to make a platform-dependent
build directory is the following (tested on Linux), maybe with
some local tweaks:
# Place yourself outside of the OpenSSL source tree. In
# this example, the environment variable OPENSSL_SOURCE
# is assumed to contain the absolute OpenSSL source directory.
mkdir -p objtree/"`uname -s`-`uname -r`-`uname -m`"
cd objtree/"`uname -s`-`uname -r`-`uname -m`"
(cd $OPENSSL_SOURCE; find . -type f) | while read F; do
mkdir -p `dirname $F`
ln -s $OPENSSL_SOURCE/$F $F
done
I understand that this method is better than there being no way at all.
However, the words "appropriate" and "recommended way" are not
appropriate here (IMHO). Other renown software packages allow for builds
outside the source tree as follows;
cd $BUILD_DIR ; # (if you're not there already)
$SRC_DIR/configure
This way, "$SRC_DIR/configure" creates a Makefile in $BUILD_DIR. The
Makefile, in turn, has SRC_DIR defined for its own usage and takes care
of proper referencing of SRC and BUILD directories.
Does the openssl roadmap foresee a further development in this area, or
is the current state deemed "the right thing"?
Thanks for your response,
Erik Leunissen
==============
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
