Commit 9de94148 authored by Richard Levitte's avatar Richard Levitte
Browse files

Rewrite CHANGES to add some commentary about the "pic" option



Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
parent ae48242c
Loading
Loading
Loading
Loading
+15 −7
Original line number Original line Diff line number Diff line
@@ -5,13 +5,17 @@
 Changes between 1.0.2f and 1.1.0  [xx XXX xxxx]
 Changes between 1.0.2f and 1.1.0  [xx XXX xxxx]


  *) Configuration change; it's now possible to build dynamic engines
  *) Configuration change; it's now possible to build dynamic engines
     without having to build shared libraries and vice versa.  The
     without having to build shared libraries and vice versa.  This
     only requirement for building dynamic engines is the presence of
     only applies to the engines in engines/, those in crypto/engine/
     the DSO module, so configuring "disable-dso" will automatically
     will always be built into libcrypto (i.e. "static").
     disable dynamic engines.  Dynamic engines are enabled by default,

     and can be disabled with "disable-dynamic-engine".
     Building dynamic engines is enabled by default; to disable, use
     This only applies to the engines in engines/, those in
     the configuration option "disable-dynamic-engine".
     crypto/engine/ will always be built into libcrypto (i.e. "static").

     The only requirements for building dynamic engines is the
     presence of the DSO module and building with position independent
     code, so they will also automatically be disabled if configuring
     with "disable-dso" or "disable pic".


     The macros OPENSSL_NO_STATIC_ENGINE and OPENSSL_NO_DYNAMIC_ENGINE
     The macros OPENSSL_NO_STATIC_ENGINE and OPENSSL_NO_DYNAMIC_ENGINE
     are also taken away from openssl/opensslconf.h, as they are
     are also taken away from openssl/opensslconf.h, as they are
@@ -24,6 +28,10 @@
     object files.  This means other libraries that use routines from
     object files.  This means other libraries that use routines from
     libcrypto / libssl can be made into shared libraries regardless
     libcrypto / libssl can be made into shared libraries regardless
     of how OpenSSL was configured.
     of how OpenSSL was configured.

     If this isn't desirable, the configuration options "disable-pic"
     or "no-pic" can be used to disable the use of PIC.  This will
     also disable building shared libraries and dynamic engines.
     [Richard Levitte]
     [Richard Levitte]


  *) Removed JPAKE code.  It was experimental and has no wide use.
  *) Removed JPAKE code.  It was experimental and has no wide use.