openssl/VMS, branch openssl-3.0.0-alpha5

Following the license change, modify the boilerplates in last few

2018-12-06T14:40:33Z

[skip ci] Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/7836)

Switch to MAJOR.MINOR.PATCH versioning and version 3.0.0-dev

2018-12-06T11:24:47Z

We're strictly use version numbers of the form MAJOR.MINOR.PATCH. Letter releases are things of days past. The most central change is that we now express the version number with three macros, one for each part of the version number: OPENSSL_VERSION_MAJOR OPENSSL_VERSION_MINOR OPENSSL_VERSION_PATCH We also provide two additional macros to express pre-release and build metadata information (also specified in semantic versioning): OPENSSL_VERSION_PRE_RELEASE OPENSSL_VERSION_BUILD_METADATA To get the library's idea of all those values, we introduce the following functions: unsigned int OPENSSL_version_major(void); unsigned int OPENSSL_version_minor(void); unsigned int OPENSSL_version_patch(void); const char *OPENSSL_version_pre_release(void); const char *OPENSSL_version_build_metadata(void); Additionally, for shared library versioning (which is out of scope in semantic versioning, but that we still need): OPENSSL_SHLIB_VERSION We also provide a macro that contains the release date. This is not part of the version number, but is extra information that we want to be able to display: OPENSSL_RELEASE_DATE Finally, also provide the following convenience functions: const char *OPENSSL_version_text(void); const char *OPENSSL_version_text_full(void); The following macros and functions are deprecated, and while currently existing for backward compatibility, they are expected to disappear: OPENSSL_VERSION_NUMBER OPENSSL_VERSION_TEXT OPENSSL_VERSION OpenSSL_version_num() OpenSSL_version() Also, this function is introduced to replace OpenSSL_version() for all indexes except for OPENSSL_VERSION: OPENSSL_info() For configuration, the option 'newversion-only' is added to disable all the macros and functions that are mentioned as deprecated above. Reviewed-by: Tim Hudson Reviewed-by: Matthias St. Pierre Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/7724)

Simplify the handling of shared library version numbers

2017-07-26T20:53:03Z

$(SHLIB_MAJOR).$(SHLIB_MINOR) is really a synonym for $(SHLIB_VERSION_NUMBER), and is therefore an added complexity, so better to use $(SHLIB_VERSION_NUMBER) directly. SHLIB_MAJOR and SHLIB_MINOR are now unused, but are kept around purely as information in case someone relies on their existence. At the same time, add support for custom shared library extensions with the three new Makefile variables SHLIB_EXT, SHLIB_EXT_SIMPLE and SHLIB_EXT_IMPORT. By default, they hold the variants of shared library extensions we support. On mingw and cygwin, SHLIB_EXT_IMPORT is defined; on all other Unix platforms, it's empty. An example to get shared libraries with a slightly different SOVER name: $ make SHLIB_EXT='.$(SHLIB_VERSION_NUMBER).so' Fixes #3902 Reviewed-by: Andy Polyakov (Merged from https://github.com/openssl/openssl/pull/3964)

VMS: Don't force symbol mixed case when building DSOs

2016-09-11T21:18:03Z

Reviewed-by: Rich Salz

dasync is an internal testing engine, so don't install it

2016-08-17T08:50:31Z

Unfortunately, it means that the VMS IVP gets a bit crippled. This will be fixed later on. Reviewed-by: Matt Caswell

VMS: have the IVP verify that a well known engine loads properly

2016-08-04T14:57:49Z

Reviewed-by: Rich Salz

VMS: If configured no-shared, don't provide shareable image logical names

2016-08-03T13:44:37Z

Reviewed-by: Rich Salz

VMS: Adjust the engines directory by adding the pointer size to its name

2016-07-10T04:40:47Z

With OpenSSL 1.1 and on, the engines are tightly tied to the shared library they're to be used with. That makes them depend on the pointer size as well as the shared library version, and this gets reflected in the name of the directory they're installed in. Reviewed-by: Rich Salz

VMS: Small cleanups

2016-07-10T04:40:47Z

Reviewed-by: Rich Salz

VMS: OSSL$EXE: needs to reflect that programs are installed in two places

2016-07-10T04:40:47Z

We're installing architecture dependent (compiled) programs in architecture specific directories, while architecture independent programs (scripts) get installed in the general programs directory. OSSL$EXE: reflects that by having two values. Reviewed-by: Rich Salz