[openssl-users] Build for Windows 2012 R2

[Michael Wojcik]

[Apologies for top-posting - Outlook doesn't handle HTML email correctly.]

The standard Windows SDK and MSVC headers need to be on the INCLUDE path.

That is, you need to run the build from a shell that has the INCLUDE environment variable set to a list of directories (delimited by semicolons) that includes directories containing the Windows SDK headers, such as windows.h, and the standard C library headers.

The PATH and LIB environment variables also need to be set appropriately

This is part of the normal Windows build environment - it's the equivalent of, say, having the build tools on the path and the system headers installed on a UNIX or Linux system - so it's not explicit in the OpenSSL documentation. It's assumed that you're building OpenSSL in an environment suitable for building other applications on your system.

Visual Studio has shortcuts for "command prompt" windows with INCLUDE, LIB, and PATH set appropriately, in its start-menu entries. It also has command scripts that set up the appropriate environment.

Michael Wojcik
Technology Specialist, Micro Focus


From: openssl-users [mailto:openssl-users-bounces at openssl.org] On Behalf Of Bossle, Jody
Sent: Monday, April 25, 2016 08:02
To: openssl-users at openssl.org
Subject: [openssl-users] Build for Windows 2012 R2

I am attempting to build the OpenSSL dlls for Windows 2012 R2.  I have MS Visual Studio 2015 Enterprise and ActivePerl installed.  During the “nmake -f ms\ntdll.mak” process I get an error message the “windows.h” file cannot be found.  I have several copies of “windows.h” on my computer: 1 each for Windows 7 and Windows 8.1, and 2 for different versions of Window 10.  I’m assuming the Windows 8.1 version would be compatible with Windows 2012 R2, however I am not sure where to put the “windows.h” file so it will be picked up during the build.  Any guidance would be greatly appreciated.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20160425/8670a50f/attachment-0001.html>