opensslv.h 4.0 KB
Newer Older
R
Rich Salz 已提交
1
/*
R
Richard Levitte 已提交
2
 * Copyright 1999-2019 The OpenSSL Project Authors. All Rights Reserved.
R
Rich Salz 已提交
3 4 5 6 7 8 9
 *
 * Licensed under the OpenSSL license (the "License").  You may not use
 * this file except in compliance with the License.  You can obtain a copy
 * in the file LICENSE in the source distribution or at
 * https://www.openssl.org/source/license.html
 */

B
Oops!  
Ben Laurie 已提交
10
#ifndef HEADER_OPENSSLV_H
11
# define HEADER_OPENSSLV_H
12

13 14 15 16
#ifdef  __cplusplus
extern "C" {
#endif

17 18
/*-
 * Numeric release version identifier:
19
 * MNNFFPPS: major minor fix patch status
20 21
 * The status nibble has one of the values 0 for development, 1 to e for betas
 * 1 to 14, and f for release.  The patch level is exactly that.
22
 * For example:
23 24
 * 0.9.3-dev      0x00903000
 * 0.9.3-beta1    0x00903001
25 26
 * 0.9.3-beta2-dev 0x00903002
 * 0.9.3-beta2    0x00903002 (same as ...beta2-dev)
27 28 29 30
 * 0.9.3          0x0090300f
 * 0.9.3a         0x0090301f
 * 0.9.4          0x0090400f
 * 1.2.3z         0x102031af
31 32 33 34 35 36 37
 *
 * For continuity reasons (because 0.9.5 is already out, and is coded
 * 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level
 * part is slightly different, by setting the highest bit.  This means
 * that 0.9.5a looks like this: 0x0090581f.  At 0.9.6, we can start
 * with 0x0090600S...
 *
38
 * (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.)
39 40
 * (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for
 *  major minor fix final patch/beta)
41
 */
M
Matt Caswell 已提交
42 43
# define OPENSSL_VERSION_NUMBER  0x10101050L
# define OPENSSL_VERSION_TEXT    "OpenSSL 1.1.1e-dev  xx XXX xxxx"
44

45 46
/*-
 * The macros below are to be used for shared library (.so, .dll, ...)
47 48 49 50 51 52 53
 * versioning.  That kind of versioning works a bit differently between
 * operating systems.  The most usual scheme is to set a major and a minor
 * number, and have the runtime loader check that the major number is equal
 * to what it was at application link time, while the minor number has to
 * be greater or equal to what it was at application link time.  With this
 * scheme, the version number is usually part of the file name, like this:
 *
54
 *      libcrypto.so.0.9
55
 *
F
FdaSilvaYY 已提交
56
 * Some unixen also make a softlink with the major version number only:
57
 *
58
 *      libcrypto.so.0
59
 *
60 61 62 63 64 65 66
 * On Tru64 and IRIX 6.x it works a little bit differently.  There, the
 * shared library version is stored in the file, and is actually a series
 * of versions, separated by colons.  The rightmost version present in the
 * library when linking an application is stored in the application to be
 * matched at run time.  When the application is run, a check is done to
 * see if the library version stored in the application matches any of the
 * versions in the version string of the library itself.
67 68 69 70 71 72
 * This version string can be constructed in any way, depending on what
 * kind of matching is desired.  However, to implement the same scheme as
 * the one used in the other unixen, all compatible versions, from lowest
 * to highest, should be part of the string.  Consecutive builds would
 * give the following versions strings:
 *
73 74 75 76 77
 *      3.0
 *      3.0:3.1
 *      3.0:3.1:3.2
 *      4.0
 *      4.0:4.1
78 79 80 81 82 83 84 85 86 87 88
 *
 * Notice how version 4 is completely incompatible with version, and
 * therefore give the breach you can see.
 *
 * There may be other schemes as well that I haven't yet discovered.
 *
 * So, here's the way it works here: first of all, the library version
 * number doesn't need at all to match the overall OpenSSL version.
 * However, it's nice and more understandable if it actually does.
 * The current library version is stored in the macro SHLIB_VERSION_NUMBER,
 * which is just a piece of text in the format "M.m.e" (Major, minor, edit).
89
 * For the sake of Tru64, IRIX, and any other OS that behaves in similar ways,
90 91 92 93
 * we need to keep a history of version numbers, which is done in the
 * macro SHLIB_VERSION_HISTORY.  The numbers are separated by colons and
 * should only keep the versions that are binary compatible with the current.
 */
94
# define SHLIB_VERSION_HISTORY ""
95
# define SHLIB_VERSION_NUMBER "1.1"
96 97


98 99 100
#ifdef  __cplusplus
}
#endif
101
#endif                          /* HEADER_OPENSSLV_H */