[Cryptography-dev] Building cryptography on Windows for Python 3.3

[Alexander Belchenko]

Hi,

I started to write an email with request for help building cryptography on
Windows for Python 3.3, but then I figured out how to get the desired
result, so now I only want to share some knowledge and also provide you a
build log in the case you're interested in compiler warnings.

Also I'd like to know it built correctly, is there any easy-to-use unittest
suite I can run? I see there tests package, but I'm not sure what is your
method to run tests in your project? Obvioulsly `python3 -m unittest` does
not work.

My intent was to build cryptography library against static libs of OpenSSL
because I had problems with running simple C code with OpenSSL dlls, I
found on StackOverflow suggestion that only linking against static
libraries would help. It does help for me.

Here is openssl directories I've used:
include: C:\OpenSSL-Win32\include
lib: C:\OpenSSL-Win32\lib\VC\static

My C code successfully linked against this set of libraries:
'libeay32MD', 'ssleay32MD', 'gdi32', 'user32', 'advapi32'

So here is my steps similar to what you wrote on Installation page:
https://cryptography.io/en/latest/installation/#on-windows

"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86
set LIB=C:\OpenSSL-Win32\lib\VC\static;%LIB%
set INCLUDE=C:\OpenSSL-Win32\include;%INCLUDE%
C:\Python33\python setup.py install

That wasn't enough because of set of libraries you need to link against. So
I just changed settings in bindings.py:

=== modified file cryptography/hazmat/bindings/openssl/binding.py

--- cryptography/hazmat/bindings/openssl/binding.py 2014-02-18 13:18:03
+0000

+++ cryptography/hazmat/bindings/openssl/binding.py 2014-02-18 13:54:26
+0000

@@ -92,7 +92,9 @@

if sys.platform != "win32":

libraries = ["crypto", "ssl"]

else: # pragma: no cover

- libraries = ["libeay32", "ssleay32", "advapi32"]

+ libraries = ["libeay32MD", "ssleay32MD",

+ "gdi32", "user32", "advapi32",

+ "Ws2_32", "Crypt32"]

 cls.ffi, cls.lib = build_ffi(cls._module_prefix, cls._modules,

_OSX_PRE_INCLUDE, _OSX_POST_INCLUDE,

With the last change I was finally able to build cryptography python
library. \o/


Attached is the build log in the case you want to see compiler errors.

Some warnings catched my eye, like this:

cryptography\hazmat\primitives\__pycache__\_cffi__xcd368b2dx4a8b9ec1.c(218)
: warning C4244: '=' : conversion from 'unsigned __int64' to 'uint8_t',
possible loss of data

or

cryptography\hazmat\bindings\__pycache__\_cffi__xabccc2b1x4bab9030.c(4386)
: warning C4308: negative integral constant converted to unsigned type

Probably you might know that everything is OK, I just wanted to test
somehow my build is OK.

Alexander.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20140218/cf96183c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: setup.log
Type: application/octet-stream
Size: 15451 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20140218/cf96183c/attachment-0001.obj>