Andrew's Garage

cite from http://developer.covenanteyes.com/building-openssl-for-visual-studio/
and some edit..

==================================================

You need to install…

• Visual Studio 2015 (this will likely work with older versions as well)
• ActivePerl 1
• Latest version of OpenSSL source-code 2 or

  $ git clone git://git.openssl.org/openssl.git
  

  $ cd openssl
  $ git config core.autocrlf false
  $ git config core.eol lf
  $ git checkout .

• nasm ( http://www.nasm.us/pub/nasm/releasebuilds/2.11.08/win32/ )

Setting up for the build

Unzip3 the OpenSSL source code into two different folders, one for the 32-bit build and one for the 64-bit build4. So, for example, you might end up with C:openssl-src-32 and C:openssl-src-64.

Building the 32-bit static libraries

1. Open the Visual Studio Command Prompt (2010)5.
2. cd to your OpenSSL source folder for 32-bit (e.g. cd C:openssl-src-32).
3. Run the following: 6
   1 2 3 4

   perl Configure VC-WIN32   no-idea no-mdc2 no-rc5  —prefix=C:Build-OpenSSL-VC-32 msdo_ms   or     msdo_nasm nmake -f msnt.mak   or  nmake -f msntdll.mak nmake -f msnt.mak install  or nmake -f msntdll.make install

Your outputs will be in C:Build-OpenSSL-VC-32.

Building the 32-bit static libraries with debug symbols

These steps will embed the debug symbols directly into the .lib files. Don’t expect to see any .pdb files.

1. Open the Visual Studio Command Prompt (2010).
2. cd to your OpenSSL source folder for 32-bit (e.g. cd C:openssl-src-32).
3. Run the following:
   1 2	perl Configure debug-VC-WIN32  no-idea no-mdc2 no-rc5   —prefix=C:Build-OpenSSL-VC-32-dbg msdo_ms

4. In a text editor (like Notepad), open msnt.mak and replace all occurrences of /Zi with /Z7. There should be three replacements.7
5. Run the following:
   1 2	nmake -f msnt.mak nmake -f msnt.mak install

Your outputs will be in C:Build-OpenSSL-VC-32-dbg. Make sure you rename them to something like libeay32-debug.lib and ssleay32-debug.lib.

Building the 64-bit static libraries

1. Open the Visual Studio x64 Win64 Command Prompt (2010) (in the Start menu).
2. cd to your OpenSSL source folder for 64-bit (e.g. cd C:openssl-src-64).
3. Run the following:
   1 2 3 4

   perl Configure VC-WIN64A  no-idea no-mdc2 no-rc5   —prefix=C:Build-OpenSSL-VC-64 msdo_win64a nmake -f msnt.mak nmake -f msnt.mak install

Your outputs will be in C:Build-OpenSSL-VC-64.

Note: The outputs of the 64-bit build are still named libeay32.lib and ssleay32.lib. You’ll have to rename them more sensibly yourself.

Building the 64-bit static libraries with debug symbols

These steps will embed the debug symbols directly into the .lib files. Don’t expect to see any .pdb files.

1. Open the Visual Studio x64 Win64 Command Prompt (2010).
2. cd to your OpenSSL source folder for 64-bit (e.g. cd C:openssl-src-64).
3. Run the following:
   1 2	perl Configure debug-VC-WIN64A  no-idea no-mdc2 no-rc5   —prefix=C:Build-OpenSSL-VC-64-dbg msdo_win64a

4. In a text editor (like Notepad), open msnt.mak and replace all occurrences of /Zi with /Z7 except on the line starting with ASM. There should be two replacements. 8
5. Run the following:
   1 2	nmake -f msnt.mak nmake -f msnt.mak install

Your outputs will be in C:Build-OpenSSL-VC-64-dbg. Make sure you rename them to something like libeay64-debug.lib and ssleay64-debug.lib.

What not to do

I tried every method under the sun to get a Windows build of OpenSSL that would link against Visual Studio projects. I learned a great deal along the way. Here’s what I learned not to do:

• Don’t blindly follow the Windows 32-bit/64-bit installation instructions provided in the OpenSSL source folder. Get guidance online.
• Don’t build OpenSSL in Cygwin. It’s easy. It won’t link against Visual Studio.
• Don’t build OpenSSL in MSYS or MinGW. It’s hard. It won’t link against Visual Studio.
• Don’t try to use NASM like the Windows installation instructions mention. It’s not necessary for Visual Studio builds. (It only supports 32-bit anyway.)
• Strawberry Perl doesn’t always work in these weird configurations. ActivePerl seemed more stable.
• Don’t try to build 32-bit and 64-bit OpenSSL in the same folder. The first build will leave artifacts that will mess up the second build. (Running a clean isn’t enough, apparently.)
• Don’t try to build 32-bit OpenSSL inside of Visual Studio’s 64-bit command prompt and vice versa. It doesn’t work.

References

These were very helpful places:

• https://github.com/freelan-developers/freelan-buildtools/blob/master/INSTALL.md