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