[EMAIL PROTECTED] - Fri Feb 27 15:44:58 2004]: > In message <[EMAIL PROTECTED]> on Fri, > 27 Feb 2004 15:42:51 +0100 (CET), Richard Levitte - VMS Whacker > <[EMAIL PROTECTED]> said: > > levitte> In message <[EMAIL PROTECTED]> on Fri, > 27 Feb 2004 15:32:26 +0100 (MET), "Stephen Henson via RT" > <[EMAIL PROTECTED]> said: > levitte> > levitte> rt> If windows.h is not included first then the #undef > X509_NAME has no > levitte> rt> effect but the structure still gets defined. When > windows.h is included > levitte> rt> X509_NAME gets #defined to whatever Windows wants it to > be and any > levitte> rt> OpenSSL source bombs with a compilation error. > levitte> > levitte> Ah, now I understand. For some reason, I mixed up "not > included > levitte> first" with "not included at all"... > levitte> > levitte> Hmm, I'm not sure what we can do about that... > > Oh wait, we could actually include windows.h just before #undef'ing > X509_NAME. It's a hack, of course, but it *would* work, at least as > long as the usual protection against multiple inclusions is present. >
There may well be circumstances where Win32 source doesn't include windows.h for some reason. If we automatically include windows.h whenever any OpenSSL header files are included this might cause bad things to happen which didn't before. IMHO the best thing to do is to keep the current behaviour but possibly include an FAQ which describes the problem and solution. Steve. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
