Time ran away...

[openssl.git] / INSTALL.VMS

diff --git a/INSTALL.VMS b/INSTALL.VMS
index cf3c81a6efd79676580fa645a87482a137d97ab4..9e852e98b394211aad573feb946d07d1dd65178b 100644 (file)
--- a/INSTALL.VMS
+++ b/INSTALL.VMS
@@ -51,7 +51,7 @@ directory.  The syntax is trhe following:
 
 Note: The RSAREF libraries are NOT INCLUDED and you have to
       download it from "ftp://ftp.rsa.com/rsaref".  You have to
-      get the ".tar-Z" file as the ".zip" file dosen't have the
+      get the ".tar-Z" file as the ".zip" file doesn't have the
       directory structure stored.  You have to extract the file
       into the [.RSAREF] directory as that is where the scripts
       will look for the files.
@@ -83,6 +83,10 @@ Note 2: if you want to compile the crypto library only, please make sure
         you have at least done a @MAKEVMS DATE and a @MAKEVMS SOFTLINKS.
         A lot of things will break if you don't.
 
+Note 3: Alpha users will get a number of informational messages when
+        compiling the [.asm]vms.mar file in the BN (bignum) part of
+        the crypto library.  These can be safely ignored.
+
 Test:
 =====
 
@@ -106,6 +110,9 @@ Installation is easy, just do the following:
 subdirectories, libraries, header files, programs and startup command
 procedures.
 
+N.B.: INSTALL.COM builds a new directory structure, different from
+the directory tree where you have now build OpenSSL.
+
 In the [.VMS] subdirectory of the installation, you will find the
 following command procedures:
 
@@ -127,15 +134,29 @@ The logical names that are set up are the following:
 
   SSLROOT       a dotted concealed logical name pointing at the
                 root directory.
-  SSLLIB        points at the directory where CRYPTORTL.OLB and
-               SSLRTL.OLB are installed.
-  SSLINCLUDE    points at the directory where the header files are
-                installed.
-  SSLEXE        points at the directory where the applications are
-                installed.
-  SSLCERTS      the place where the certificates are stored.
-  SSLPRIVATE    I'm actually not sure what this is used for.
 
+  SSLCERTS      Initially an empty directory, this is the default
+               location for certificate files.
+  SSLMISC      Various scripts.
+  SSLPRIVATE   Initially an empty directory, this is the default
+               location for private key files.
+
+  SSLEXE        Contains the openssl binary and a few other utility
+               programs.
+  SSLINCLUDE    Contains the header files needed if you want to
+               compile programs with libcrypto or libssl.
+  SSLLIB        Contains the OpenSSL library files (LIBCRYPTO.OLB
+               and LIBSSL.OLB) themselves.
+
+  OPENSSL      Same as SSLINCLUDE.  This is because the standard
+               way to include OpenSSL header files from version
+               0.9.3 and on is:
+
+                       #include <openssl/header.h>
+
+               For more info on this issue, see the INSTALL. file
+               (the NOTE in section 4 of "Installation in Detail").
+               You don't need to "deleting old header files"!!!
 
 Backward portability:
 =====================
@@ -154,7 +175,7 @@ dependent on the OpenVMS version or the C library version, *and* you
 can use those macros to simulate older OpenVMS or C library versions,
 by defining the macros _VMS_V6_SOURCE, __VMS_VER and __CTRL_VER with
 correct values.  In the compilation scripts, I've provided the possibility
-for the user to influense the creation of such macros, through a bunch of
+for the user to influence the creation of such macros, through a bunch of
 symbols, all having names starting with USER_.  Here's the list of them:
 
   USER_CCFLAGS          - Used to give additional qualifiers to the
@@ -202,3 +223,23 @@ for further info.
 -- 
 Richard Levitte <richard@levitte.org>
 1999-03-09
+
+
+TODO:
+=====
+
+There are a few things that need to be worked out in the VMS version of
+OpenSSL, still:
+
+- Description files. ("Makefile's" :-))
+- Script code to link an already compiled build tree.
+- A VMSINSTALlable version (way in the future, unless someone else hacks).
+- shareable images (DLL for you Windows folks).
+
+There may be other things that I have missed and that may be desirable.
+Please send mail to <openssl-users@openssl.org> or to me directly if you
+have any ideas.
+
+--
+Richard Levitte <richard@levitte.org>
+1999-05-24