Comment 10 for bug 364185

Hi Žiga,

Just a follow-up. I did some testing with the client_CA branch. I built OpenSSL with VS.NET2003 and then built pyOpenSSL for Python 2.3, 2.4, and 2.5 with the same. This all worked, and the tests for all the resulting builds passed. I also used the slproweb.com OpenSSL installer (what I've actually been using for all versions of Python so far) and built pyOpenSSL with VS2008 for Python 2.6 against that. This also worked and produced a passing test suite.

I wasn't able to build pyOpenSSL for Python 2.3, 2.4, or 2.5 with mingw, though. This was the failure:

  gcc: C:\OpenSSL-VS.NET2003\lib\MinGW\ssleay32.a: No such file or directory
  gcc: C:\OpenSSL-VS.NET2003\lib\MinGW\libeay32.a: No such file or directory

I expect this is because building OpenSSL with VS doesn't produce the pieces mingw requires, though. At this point, while I'd be sad to see mingw support go, I'm sick enough of Windows build issues to not feel strongly enough to do much about it. Working VS support is sufficient to provide all the functionality that users have required (ie, a binary Windows installer).