Eneboo - Documentación para desarrolladores
src/libdigidoc/openssl/crypto/opensslv.h
Ir a la documentación de este archivo.
00001 #ifndef HEADER_OPENSSLV_H
00002 #define HEADER_OPENSSLV_H
00003 
00004 /* Numeric release version identifier:
00005  * MNNFFPPS: major minor fix patch status
00006  * The status nibble has one of the values 0 for development, 1 to e for betas
00007  * 1 to 14, and f for release.  The patch level is exactly that.
00008  * For example:
00009  * 0.9.3-dev      0x00903000
00010  * 0.9.3-beta1    0x00903001
00011  * 0.9.3-beta2-dev 0x00903002
00012  * 0.9.3-beta2    0x00903002 (same as ...beta2-dev)
00013  * 0.9.3          0x0090300f
00014  * 0.9.3a         0x0090301f
00015  * 0.9.4          0x0090400f
00016  * 1.2.3z         0x102031af
00017  *
00018  * For continuity reasons (because 0.9.5 is already out, and is coded
00019  * 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level
00020  * part is slightly different, by setting the highest bit.  This means
00021  * that 0.9.5a looks like this: 0x0090581f.  At 0.9.6, we can start
00022  * with 0x0090600S...
00023  *
00024  * (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.)
00025  * (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for
00026  *  major minor fix final patch/beta)
00027  */
00028 #define OPENSSL_VERSION_NUMBER  0x009080ffL
00029 #ifdef OPENSSL_FIPS
00030 #define OPENSSL_VERSION_TEXT    "OpenSSL 0.9.8o-fips 01 Jun 2010"
00031 #else
00032 #define OPENSSL_VERSION_TEXT    "OpenSSL 0.9.8o 01 Jun 2010"
00033 #endif
00034 #define OPENSSL_VERSION_PTEXT   " part of " OPENSSL_VERSION_TEXT
00035 
00036 
00037 /* The macros below are to be used for shared library (.so, .dll, ...)
00038  * versioning.  That kind of versioning works a bit differently between
00039  * operating systems.  The most usual scheme is to set a major and a minor
00040  * number, and have the runtime loader check that the major number is equal
00041  * to what it was at application link time, while the minor number has to
00042  * be greater or equal to what it was at application link time.  With this
00043  * scheme, the version number is usually part of the file name, like this:
00044  *
00045  *      libcrypto.so.0.9
00046  *
00047  * Some unixen also make a softlink with the major verson number only:
00048  *
00049  *      libcrypto.so.0
00050  *
00051  * On Tru64 and IRIX 6.x it works a little bit differently.  There, the
00052  * shared library version is stored in the file, and is actually a series
00053  * of versions, separated by colons.  The rightmost version present in the
00054  * library when linking an application is stored in the application to be
00055  * matched at run time.  When the application is run, a check is done to
00056  * see if the library version stored in the application matches any of the
00057  * versions in the version string of the library itself.
00058  * This version string can be constructed in any way, depending on what
00059  * kind of matching is desired.  However, to implement the same scheme as
00060  * the one used in the other unixen, all compatible versions, from lowest
00061  * to highest, should be part of the string.  Consecutive builds would
00062  * give the following versions strings:
00063  *
00064  *      3.0
00065  *      3.0:3.1
00066  *      3.0:3.1:3.2
00067  *      4.0
00068  *      4.0:4.1
00069  *
00070  * Notice how version 4 is completely incompatible with version, and
00071  * therefore give the breach you can see.
00072  *
00073  * There may be other schemes as well that I haven't yet discovered.
00074  *
00075  * So, here's the way it works here: first of all, the library version
00076  * number doesn't need at all to match the overall OpenSSL version.
00077  * However, it's nice and more understandable if it actually does.
00078  * The current library version is stored in the macro SHLIB_VERSION_NUMBER,
00079  * which is just a piece of text in the format "M.m.e" (Major, minor, edit).
00080  * For the sake of Tru64, IRIX, and any other OS that behaves in similar ways,
00081  * we need to keep a history of version numbers, which is done in the
00082  * macro SHLIB_VERSION_HISTORY.  The numbers are separated by colons and
00083  * should only keep the versions that are binary compatible with the current.
00084  */
00085 #define SHLIB_VERSION_HISTORY ""
00086 #define SHLIB_VERSION_NUMBER "0.9.8"
00087 
00088 
00089 #endif /* HEADER_OPENSSLV_H */
 Todo Clases Namespaces Archivos Funciones Variables 'typedefs' Enumeraciones Valores de enumeraciones Propiedades Amigas 'defines'