jpayne@69: /*
jpayne@69:  * Copyright 1999-2023 The OpenSSL Project Authors. All Rights Reserved.
jpayne@69:  *
jpayne@69:  * Licensed under the OpenSSL license (the "License").  You may not use
jpayne@69:  * this file except in compliance with the License.  You can obtain a copy
jpayne@69:  * in the file LICENSE in the source distribution or at
jpayne@69:  * https://www.openssl.org/source/license.html
jpayne@69:  */
jpayne@69: 
jpayne@69: #ifndef HEADER_OPENSSLV_H
jpayne@69: # define HEADER_OPENSSLV_H
jpayne@69: 
jpayne@69: #ifdef  __cplusplus
jpayne@69: extern "C" {
jpayne@69: #endif
jpayne@69: 
jpayne@69: /*-
jpayne@69:  * Numeric release version identifier:
jpayne@69:  * MNNFFPPS: major minor fix patch status
jpayne@69:  * The status nibble has one of the values 0 for development, 1 to e for betas
jpayne@69:  * 1 to 14, and f for release.  The patch level is exactly that.
jpayne@69:  * For example:
jpayne@69:  * 0.9.3-dev      0x00903000
jpayne@69:  * 0.9.3-beta1    0x00903001
jpayne@69:  * 0.9.3-beta2-dev 0x00903002
jpayne@69:  * 0.9.3-beta2    0x00903002 (same as ...beta2-dev)
jpayne@69:  * 0.9.3          0x0090300f
jpayne@69:  * 0.9.3a         0x0090301f
jpayne@69:  * 0.9.4          0x0090400f
jpayne@69:  * 1.2.3z         0x102031af
jpayne@69:  *
jpayne@69:  * For continuity reasons (because 0.9.5 is already out, and is coded
jpayne@69:  * 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level
jpayne@69:  * part is slightly different, by setting the highest bit.  This means
jpayne@69:  * that 0.9.5a looks like this: 0x0090581f.  At 0.9.6, we can start
jpayne@69:  * with 0x0090600S...
jpayne@69:  *
jpayne@69:  * (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.)
jpayne@69:  * (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for
jpayne@69:  *  major minor fix final patch/beta)
jpayne@69:  */
jpayne@69: # define OPENSSL_VERSION_NUMBER  0x1010117fL
jpayne@69: # define OPENSSL_VERSION_TEXT    "OpenSSL 1.1.1w  11 Sep 2023"
jpayne@69: 
jpayne@69: /*-
jpayne@69:  * The macros below are to be used for shared library (.so, .dll, ...)
jpayne@69:  * versioning.  That kind of versioning works a bit differently between
jpayne@69:  * operating systems.  The most usual scheme is to set a major and a minor
jpayne@69:  * number, and have the runtime loader check that the major number is equal
jpayne@69:  * to what it was at application link time, while the minor number has to
jpayne@69:  * be greater or equal to what it was at application link time.  With this
jpayne@69:  * scheme, the version number is usually part of the file name, like this:
jpayne@69:  *
jpayne@69:  *      libcrypto.so.0.9
jpayne@69:  *
jpayne@69:  * Some unixen also make a softlink with the major version number only:
jpayne@69:  *
jpayne@69:  *      libcrypto.so.0
jpayne@69:  *
jpayne@69:  * On Tru64 and IRIX 6.x it works a little bit differently.  There, the
jpayne@69:  * shared library version is stored in the file, and is actually a series
jpayne@69:  * of versions, separated by colons.  The rightmost version present in the
jpayne@69:  * library when linking an application is stored in the application to be
jpayne@69:  * matched at run time.  When the application is run, a check is done to
jpayne@69:  * see if the library version stored in the application matches any of the
jpayne@69:  * versions in the version string of the library itself.
jpayne@69:  * This version string can be constructed in any way, depending on what
jpayne@69:  * kind of matching is desired.  However, to implement the same scheme as
jpayne@69:  * the one used in the other unixen, all compatible versions, from lowest
jpayne@69:  * to highest, should be part of the string.  Consecutive builds would
jpayne@69:  * give the following versions strings:
jpayne@69:  *
jpayne@69:  *      3.0
jpayne@69:  *      3.0:3.1
jpayne@69:  *      3.0:3.1:3.2
jpayne@69:  *      4.0
jpayne@69:  *      4.0:4.1
jpayne@69:  *
jpayne@69:  * Notice how version 4 is completely incompatible with version, and
jpayne@69:  * therefore give the breach you can see.
jpayne@69:  *
jpayne@69:  * There may be other schemes as well that I haven't yet discovered.
jpayne@69:  *
jpayne@69:  * So, here's the way it works here: first of all, the library version
jpayne@69:  * number doesn't need at all to match the overall OpenSSL version.
jpayne@69:  * However, it's nice and more understandable if it actually does.
jpayne@69:  * The current library version is stored in the macro SHLIB_VERSION_NUMBER,
jpayne@69:  * which is just a piece of text in the format "M.m.e" (Major, minor, edit).
jpayne@69:  * For the sake of Tru64, IRIX, and any other OS that behaves in similar ways,
jpayne@69:  * we need to keep a history of version numbers, which is done in the
jpayne@69:  * macro SHLIB_VERSION_HISTORY.  The numbers are separated by colons and
jpayne@69:  * should only keep the versions that are binary compatible with the current.
jpayne@69:  */
jpayne@69: # define SHLIB_VERSION_HISTORY ""
jpayne@69: # define SHLIB_VERSION_NUMBER "1.1"
jpayne@69: 
jpayne@69: 
jpayne@69: #ifdef  __cplusplus
jpayne@69: }
jpayne@69: #endif
jpayne@69: #endif                          /* HEADER_OPENSSLV_H */