[EMAIL PROTECTED] wrote:
Hi,
5. Added -DWIN32_LEAN_AND_MEAN and drop the conflict undef of x509.h
While I don't mind having to compile the library itself with "special"
flags, the above implies that every _user_ of OpenSSL who includes
x509.h has to either use -DWIN32_LEAN_AND_MEAN as well or that he is
going to have to add those undefs himself, so IMHO this is something
which really should be done by openssl headers themselves, even if
that means a bit more work and occassionally doesn't work (i.e. when
MS adds yet another conflicting definition to their headers...).
Regards,
Stefan
Always MSDN information help to sort out VC problems with inclusion of
windows headers. Definition of WIN32_LEAN_AND_MEAN prevent not only
inclusion winsock header but wincrypt and some other headers. Definition
of NOCRYPT prevent only wincrypt if WIN32_LEAN_AND_MEAN is not defined.
Application is responsible how to order headers and how to use defines
to get type/function declaration, to avoid conflicts and etc..
In mingw32 case windows.h don't include wincrypt header.
If WIN32_LEAN_AND_MEAN isn't defined: If _WIN32_WINNT is greater or
equal to 0x0400 mingw32 windows header include winsock2 otherwise
winsock. This inclusion of winsock2 is not compatible to MSVC headers
but is more user friendly.
Roumen
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
