[openssl-commits] [openssl] master update
Richard Levitte
levitte at openssl.org
Sat Feb 20 23:35:22 UTC 2016
The branch master has been updated
via 380f047707de4f8c22eeaec63f481d4734efe7a5 (commit)
from ea80a25e812520ebcaa437aec90ac2b9791df4b2 (commit)
- Log -----------------------------------------------------------------
commit 380f047707de4f8c22eeaec63f481d4734efe7a5
Author: Richard Levitte <levitte at openssl.org>
Date: Sat Feb 20 17:06:54 2016 +0100
Document the last configuration changes
Reviewed-by: Rich Salz <rsalz at openssl.org>
-----------------------------------------------------------------------
Summary of changes:
CHANGES | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/CHANGES b/CHANGES
index ee1d374..d60d655 100644
--- a/CHANGES
+++ b/CHANGES
@@ -4,6 +4,28 @@
Changes between 1.0.2f and 1.1.0 [xx XXX xxxx]
+ *) Configuration change; it's now possible to build dynamic engines
+ without having to build shared libraries and vice versa. The
+ only requirement for building dynamic engines is the presence of
+ the DSO module, so configuring "disable-dso" will automatically
+ disable dynamic engines. Dynamic engines are enabled by default,
+ and can be disabled with "enable-static-engine".
+ This only applies to the engines in engines/, those in
+ crypto/engine/ will always be built into libcrypto (i.e. "static").
+
+ The macros OPENSSL_NO_STATIC_ENGINE and OPENSSL_NO_DYNAMIC_ENGINE
+ are also taken away from openssl/opensslconf.h, as they are
+ irrelevant.
+ [Richard Levitte]
+
+ *) Configuration change; if there is a known flag to compile
+ position independent code, it will always be applied on the
+ libcrypto and libssl object files, and never on the application
+ object files. This means other libraries that use routines from
+ libcrypto / libssl can be made into shared libraries regardless
+ of how OpenSSL was configured.
+ [Richard Levitte]
+
*) Removed JPAKE code. It was experimental and has no wide use.
[Rich Salz]
More information about the openssl-commits
mailing list