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