| 63 | | It's necessary to build OpenSSL to build OpenVPN as described [http://ehsanakhgari.org/blog/2008-05-04/compiling-openvpn-windows here]. |
| | 63 | First download the latest (0.9.8) release from [http://www.openssl.org/source here] and extract it somewhere. Using the latest one ensures there are no (known) security holes in OpenSSL. For the most part you can then follow the instructions in ''INSTALL.W32'' and ''INSTALL.W64'' files. Before you start, though, launch the ''Visual Studio 2008 x64 Cross Tools Command Prompt'', which can be found from the ''Start menu''. Unlike the standard command prompt it has all the paths to VC binaries set correctly. |
| | 64 | |
| | 65 | From within this command prompt you'll first configure OpenSSL using the provided Perl script: |
| | 66 | |
| | 67 | {{{ |
| | 68 | cd c:\<directory-with-openssl-sources> |
| | 69 | perl Configure VC-WIN32 --prefix=c:/<openssl-install-directory> |
| | 70 | }}} |
| | 71 | |
| | 72 | Some of the crypto routines are written in assembler to increase performance, so you need to/should use an assembler (e.g. MASM) in the next step: |
| | 73 | |
| | 74 | {{{ |
| | 75 | ms\do_masm |
| | 76 | }}} |
| | 77 | |
| | 78 | Next compile OpenSSL using the provided scripts: |
| | 79 | |
| | 80 | {{{ |
| | 81 | nmake -f ms\ntdll.mak |
| | 82 | nmake -f ms\ntdll.mak test |
| | 83 | nmake -f ms\ntdll.mak install |
| | 84 | }}} |
| | 85 | |
| | 86 | In theory this should work. However, you'll most likely encounter issues with (trivial?) compiler warnings stopping the entire build. To circumvent this remove the ''/WX'' flag in the makefile as suggested in INSTALL.W32 files. This is harder than it seems for two reasons: |
| | 87 | |
| | 88 | * The correct makefile is ''ms\ntdll.mak'' (not ''Makefile'' in build root) |
| | 89 | * You need to use ''Wordpad'' or other UNIX linefeed-aware editor to open the makefile |
