williamr@2: #ifndef HEADER_OPENSSLV_H
williamr@2: #define HEADER_OPENSSLV_H
williamr@2: 
williamr@2: /* Numeric release version identifier:
williamr@2:  * MNNFFPPS: major minor fix patch status
williamr@2:  * The status nibble has one of the values 0 for development, 1 to e for betas
williamr@2:  * 1 to 14, and f for release.  The patch level is exactly that.
williamr@2:  * For example:
williamr@2:  * 0.9.3-dev	  0x00903000
williamr@2:  * 0.9.3-beta1	  0x00903001
williamr@2:  * 0.9.3-beta2-dev 0x00903002
williamr@2:  * 0.9.3-beta2    0x00903002 (same as ...beta2-dev)
williamr@2:  * 0.9.3	  0x0090300f
williamr@2:  * 0.9.3a	  0x0090301f
williamr@2:  * 0.9.4	  0x0090400f
williamr@2:  * 1.2.3z	  0x102031af
williamr@2:  *
williamr@2:  * For continuity reasons (because 0.9.5 is already out, and is coded
williamr@2:  * 0x00905100), between 0.9.5 and 0.9.6 the coding of the patch level
williamr@2:  * part is slightly different, by setting the highest bit.  This means
williamr@2:  * that 0.9.5a looks like this: 0x0090581f.  At 0.9.6, we can start
williamr@2:  * with 0x0090600S...
williamr@2:  *
williamr@2:  * (Prior to 0.9.3-dev a different scheme was used: 0.9.2b is 0x0922.)
williamr@2:  * (Prior to 0.9.5a beta1, a different scheme was used: MMNNFFRBB for
williamr@2:  *  major minor fix final patch/beta)
williamr@2:  */
williamr@2: 
williamr@2: #if (defined(__SYMBIAN32__) && !defined(SYMBIAN))
williamr@2: #define SYMBIAN
williamr@2: #endif
williamr@2:   
williamr@2: #define OPENSSL_VERSION_NUMBER	0x0090807fL
williamr@2: #ifdef OPENSSL_FIPS
williamr@2: #define OPENSSL_VERSION_TEXT	"OpenSSL 0.9.8g-fips 19 Oct 2007"
williamr@2: #else
williamr@2: #define OPENSSL_VERSION_TEXT	"OpenSSL 0.9.8g 19 Oct 2007"
williamr@2: #endif
williamr@2: #define OPENSSL_VERSION_PTEXT	" part of " OPENSSL_VERSION_TEXT
williamr@2: 
williamr@2: 
williamr@2: /* The macros below are to be used for shared library (.so, .dll, ...)
williamr@2:  * versioning.  That kind of versioning works a bit differently between
williamr@2:  * operating systems.  The most usual scheme is to set a major and a minor
williamr@2:  * number, and have the runtime loader check that the major number is equal
williamr@2:  * to what it was at application link time, while the minor number has to
williamr@2:  * be greater or equal to what it was at application link time.  With this
williamr@2:  * scheme, the version number is usually part of the file name, like this:
williamr@2:  *
williamr@2:  *	libcrypto.so.0.9
williamr@2:  *
williamr@2:  * Some unixen also make a softlink with the major verson number only:
williamr@2:  *
williamr@2:  *	libcrypto.so.0
williamr@2:  *
williamr@2:  * On Tru64 and IRIX 6.x it works a little bit differently.  There, the
williamr@2:  * shared library version is stored in the file, and is actually a series
williamr@2:  * of versions, separated by colons.  The rightmost version present in the
williamr@2:  * library when linking an application is stored in the application to be
williamr@2:  * matched at run time.  When the application is run, a check is done to
williamr@2:  * see if the library version stored in the application matches any of the
williamr@2:  * versions in the version string of the library itself.
williamr@2:  * This version string can be constructed in any way, depending on what
williamr@2:  * kind of matching is desired.  However, to implement the same scheme as
williamr@2:  * the one used in the other unixen, all compatible versions, from lowest
williamr@2:  * to highest, should be part of the string.  Consecutive builds would
williamr@2:  * give the following versions strings:
williamr@2:  *
williamr@2:  *	3.0
williamr@2:  *	3.0:3.1
williamr@2:  *	3.0:3.1:3.2
williamr@2:  *	4.0
williamr@2:  *	4.0:4.1
williamr@2:  *
williamr@2:  * Notice how version 4 is completely incompatible with version, and
williamr@2:  * therefore give the breach you can see.
williamr@2:  *
williamr@2:  * There may be other schemes as well that I haven't yet discovered.
williamr@2:  *
williamr@2:  * So, here's the way it works here: first of all, the library version
williamr@2:  * number doesn't need at all to match the overall OpenSSL version.
williamr@2:  * However, it's nice and more understandable if it actually does.
williamr@2:  * The current library version is stored in the macro SHLIB_VERSION_NUMBER,
williamr@2:  * which is just a piece of text in the format "M.m.e" (Major, minor, edit).
williamr@2:  * For the sake of Tru64, IRIX, and any other OS that behaves in similar ways,
williamr@2:  * we need to keep a history of version numbers, which is done in the
williamr@2:  * macro SHLIB_VERSION_HISTORY.  The numbers are separated by colons and
williamr@2:  * should only keep the versions that are binary compatible with the current.
williamr@2:  */
williamr@2: #define SHLIB_VERSION_HISTORY ""
williamr@2: #define SHLIB_VERSION_NUMBER "0.9.8"
williamr@2: 
williamr@2: 
williamr@2: #endif /* HEADER_OPENSSLV_H */