Rework building: VMS changes to handle extensions and product names

Add platform::VMS, which is a generic VMS module.  Additional modules
to support specific building aspects (such as specific compilers) may
be added later, but since we currently work on file names and those
are generic enough, this is also enough.

This reworks Configurations/descrip.mms.tmpl to work out product names
in platform::VMS terms.  Something to be noted is that the new
functionality ignores the *_extension config attributes, as they were
never used.  VMS is very consistent in its use of extensions, so there
is no reason to believe much will change in this respect.

Reviewed-by: Tim Hudson <tjh@openssl.org>
Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/7473)

1 files changed, 4 insertions, 7 deletions

diff --git a/util/unlocal_shlib.com.in b/util/unlocal_shlib.com.in
index dd4fd2a9dd..f9ae76b47b 100644
--- a/util/unlocal_shlib.com.in
+++ b/util/unlocal_shlib.com.in
@@ -1,17 +1,14 @@
 ${-
-  use File::Spec::Functions qw(rel2abs);
-
-  my $bldtop = rel2abs($config{builddir});
-  our %names = ( map { $_ => $bldtop.$_.".EXE" }
-                 map { $unified_info{sharednames}->{$_} || () }
-                 @{$unified_info{libraries}} );
+  our %names = ( map { platform->sharedname($_) =>
+                           $bldtop.platform->sharedlib($_) }
+                 @{$unified_info{install}->{libraries}} );
   "" -}
 $       ! Remove the local environment created by local_shlib.com
 $
 $       OPENSSL_NAMES := OPENSSL_NAMES_'F$GETJPI("","PID")'
 $       IF F$TRNLNM("OSSL_FLAG",OPENSSL_NAMES) .EQS. "" THEN EXIT 0
 $
-$       NAMES := {- join(",", keys %names); -}
+$       NAMES := {- join(",", sort keys %names); -}
 $       I = 0
 $       LOOP:
 $           E = F$ELEMENT(I,",",NAMES)