Build dynamic engines even if configured "no-shared"
authorRichard Levitte <levitte@openssl.org>
Fri, 19 Feb 2016 21:08:37 +0000 (22:08 +0100)
committerRichard Levitte <levitte@openssl.org>
Sat, 20 Feb 2016 15:51:31 +0000 (16:51 +0100)
commit343ec2b083b82ccf9ce96020bc95320390296f1f
treee159c94c1ebe2bb60fec21911c095b74e15865fe
parent45502bfe19fb03c9f343b03fa6434ee0bece8428
Build dynamic engines even if configured "no-shared"

Until now, the engines in engines/ were only built as dynamicaly
loadable ones if shared libraries were built.

We not dissociate the two and can build dynamicaly loadable engines
even if we only build static libcrypto and libssl.  This is controlled
with the option (enable|disable|no)-static-engine, defaulting to
no-static-engine.

Note that the engines in crypto/engine/ (dynamic and cryptodev) will
always be built into libcrypto.

Reviewed-by: Rich Salz <rsalz@openssl.org>
Configure
Makefile.in
engines/Makefile.in
engines/build.info
util/mk1mf.pl