openssl/VMS
Richard Levitte e8fb12957a Versioning engines default location: the VMS case
OpenSSL engines are tied to the OpenSSL shared library versions,
starting with OpenSSL 1.1.  We therefore need to install them in
directories which have the shared library version in it's name, to
easily allow multiple OpenSSL versions to be installed at the same
time.

For VMS, the change is a bit more involved, primarly because the top
installation directory was already versioned, *as well as* some of the
files inside.  That's a bit too much.  Version numbering in files is
also a bit different on VMS.  The engines for shared library version
1.1 will therefore end up in OSSL$INSTROOT:[ENGINES0101.'arch']

('arch' is the architecture we build for)

Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-07-07 15:07:32 +02:00
..
engine.opt unified build scheme: add a "unified" template for VMS descrip.mms 2016-02-10 14:36:32 +01:00
openssl_ivp.com.in VMS: Add installation verification procedure 2016-07-02 15:50:44 +02:00
openssl_shutdown.com.in Versioning engines default location: the VMS case 2016-07-07 15:07:32 +02:00
openssl_startup.com.in Versioning engines default location: the VMS case 2016-07-07 15:07:32 +02:00
openssl_utils.com.in Install the openssl app with version number on VMS 2016-07-02 15:49:45 +02:00
test-includes.com A test script to check on the header files 2000-01-18 08:10:28 +00:00
translatesyms.pl Copyright consolidation: perl files 2016-04-20 09:45:40 -04:00
VMSify-conf.pl Copyright consolidation: perl files 2016-04-20 09:45:40 -04:00