The most recent platform SDK (the one for Windows2000) has a new file,
WinCrypt.h, that includes lines like:
#define X509_NAME ((LPCSTR)6)
Unless you #define NOCRYPT, then windows.h will #include this file.
This will generally be okay, except in cases where you want to
mix OpenSSL and CryptoAPI in a single file, in which case things
like the following should work:
#include <windows.h>
#define X509_NAME SSL_X509_NAME
#include <openssl/x509.h>
#undef X509_NAME
and then using SSL_X509_NAME as the datatype in your code. This will
be tedious because there are many name conflicts, not just one.
Perhaps some new "winstart" and "winend" headers could be created to
capture all of these in once place? Whatever...
/r$
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
