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