They both build fine. For OpenSSL, follow the instructions at Building OpenSSL 1.0.1g on 64-bit Windows Pro 8.1 with Windows SDK 7.1. For Vim, refer to Building and Installing gVim on Windows 8.1 Pro.
Since 7.4.393, you can build GVim with DirectX support on Windows Vista and later. Subjectively, things look much better to me.
If you run into problems with Vim, make sure Windows SDK 7.1 is installed, and add its
include directory (and only the
include) to your header search path (for
set INCLUDE=%INCLUDE%;C:\Program Files\Microsoft SDKs\Windows\v7.1\Include
The correct include path to point to the SDK included with the VS2013CE would be:
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include
Again, this is just for the
Win32.mak file, so it doesn’t make a huge difference, but, still.
After building OpenSSL, you can do:
set OPENSSL_PREFIX=c:\your-openssl-top-dir cpanm LWP::Protocol::https
That reminds me, I should support OPENSSL_PREFIX in
Crypt::SSLeay as well.
On my system, a test in t\io-socket-ip.t fails for a reason I cannot figure out. It may have to do with peculiarities of my system, so I force installed IO::Socket::SSL.