switch to static linking on windows and update installation page

fixes #1121

crypt32, gdi32, user32, and ws2_32 are required to make it statically link successfully, but are not required for dynamic linking.

At the moment this results in a wheel that is ~978k for 64-bit windows (as opposed to 248kb for our previous release). Not a big deal.
For someone operating their own, automated, windows infrastructure, it
would be a significant regression to no longer support dynamic linking on
Windows.


On Mon, Jun 30, 2014 at 2:44 PM, Paul Kehrer <notifications@github.com>
wrote:

> In cryptography/hazmat/bindings/openssl/binding.py:
>
> > @@ -98,6 +98,10 @@ def _ensure_ffi_initialized(cls):
> >              libraries = ["crypto", "ssl"]
> >          else:  # pragma: no cover
> >              libraries = ["libeay32", "ssleay32", "advapi32"]
> > +            libraries = [
> > +                "libeay32mt", "ssleay32mt", "advapi32",
> > +                "crypt32", "gdi32", "user32", "ws2_32"
> > +            ]
>
> I'm not aware of one. It might be worth adding a new section to our docs
> that talks about static vs dynamic and explains how to do it on our
> supported platforms, but that should probably be filed as a separate issue.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/pyca/cryptography/pull/1206/files#r14377687>.
>



-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: 125F 5C67 DFE9 4084