crypto/opensslv.h

   1 #ifndef HEADER_OPENSSLV_H
   2 # define HEADER_OPENSSLV_H
   3
   4 #ifdef  __cplusplus
   5 extern "C" {
   6 #endif
   7
   8 /*-
   9  * Numeric release version identifier:
  10  * MNNFFPPS: major minor fix patch status
  11  * The status nibble has one of the values 0 for development, 1 to e for betas
  12  * 1 to 14, and f for release.  The patch level is exactly that.
  13  * For example:
  14  * 0.9.3-dev      0x00903000
  15  * 0.9.3-beta1    0x00903001
  16  * 0.9.3-beta2-dev 0x00903002
  17  * 0.9.3-beta2    0x00903002 (same as ...beta2-dev)
  18  * 0.9.3          0x0090300f
  19  * 0.9.3a         0x0090301f
  20  * 0.9.4          0x0090400f
  21  * 1.2.3z         0x102031af
  22  *
  23  * For continuity reasons (because 0.9.5 is already out, and is coded
  24  * 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level
  25  * part is slightly different, by setting the highest bit.  This means
  26  * that 0.9.5a looks like this: 0x0090581f.  At 0.9.6, we can start
  27  * with 0x0090600S...
  28  *
  29  * (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.)
  30  * (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for
  31  *  major minor fix final patch/beta)
  32  */
  33 # define OPENSSL_VERSION_NUMBER  0x10100000L
  34 # ifdef OPENSSL_FIPS
  35 #  define OPENSSL_VERSION_TEXT    "OpenSSL 1.1.0-fips-dev xx XXX xxxx"
  36 # else
  37 #  define OPENSSL_VERSION_TEXT    "OpenSSL 1.1.0-dev xx XXX xxxx"
  38 # endif
  39 # define OPENSSL_VERSION_PTEXT   " part of " OPENSSL_VERSION_TEXT
  40
  41 /*-
  42  * The macros below are to be used for shared library (.so, .dll, ...)
  43  * versioning.  That kind of versioning works a bit differently between
  44  * operating systems.  The most usual scheme is to set a major and a minor
  45  * number, and have the runtime loader check that the major number is equal
  46  * to what it was at application link time, while the minor number has to
  47  * be greater or equal to what it was at application link time.  With this
  48  * scheme, the version number is usually part of the file name, like this:
  49  *
  50  *      libcrypto.so.0.9
  51  *
  52  * Some unixen also make a softlink with the major verson number only:
  53  *
  54  *      libcrypto.so.0
  55  *
  56  * On Tru64 and IRIX 6.x it works a little bit differently.  There, the
  57  * shared library version is stored in the file, and is actually a series
  58  * of versions, separated by colons.  The rightmost version present in the
  59  * library when linking an application is stored in the application to be
  60  * matched at run time.  When the application is run, a check is done to
  61  * see if the library version stored in the application matches any of the
  62  * versions in the version string of the library itself.
  63  * This version string can be constructed in any way, depending on what
  64  * kind of matching is desired.  However, to implement the same scheme as
  65  * the one used in the other unixen, all compatible versions, from lowest
  66  * to highest, should be part of the string.  Consecutive builds would
  67  * give the following versions strings:
  68  *
  69  *      3.0
  70  *      3.0:3.1
  71  *      3.0:3.1:3.2
  72  *      4.0
  73  *      4.0:4.1
  74  *
  75  * Notice how version 4 is completely incompatible with version, and
  76  * therefore give the breach you can see.
  77  *
  78  * There may be other schemes as well that I haven't yet discovered.
  79  *
  80  * So, here's the way it works here: first of all, the library version
  81  * number doesn't need at all to match the overall OpenSSL version.
  82  * However, it's nice and more understandable if it actually does.
  83  * The current library version is stored in the macro SHLIB_VERSION_NUMBER,
  84  * which is just a piece of text in the format "M.m.e" (Major, minor, edit).
  85  * For the sake of Tru64, IRIX, and any other OS that behaves in similar ways,
  86  * we need to keep a history of version numbers, which is done in the
  87  * macro SHLIB_VERSION_HISTORY.  The numbers are separated by colons and
  88  * should only keep the versions that are binary compatible with the current.
  89  */
  90 # define SHLIB_VERSION_HISTORY ""
  91 # define SHLIB_VERSION_NUMBER "1.1.0"
  92
  93
  94 #ifdef  __cplusplus
  95 }
  96 #endif
  97 #endif                          /* HEADER_OPENSSLV_H */