Build for Windows 2012 R2

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Build for Windows 2012 R2

Bossle, Jody

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.

 

cid:image001.png@01D1331E.96FD6780

 

Joseph A. Bossle III, “Jody”

Sr. Technical Consultant / Global Information Technology

Baxter International Inc.

One Baxter Parkway / Deerfield, Illinois 60015

T 224.270.3563  /  M 630.650.9413

[hidden email]

 


--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Reply | Threaded
Open this post in threaded view
|

Re: 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:[hidden email]] On Behalf Of Bossle, Jody
Sent: Monday, April 25, 2016 08:02
To: [hidden email]
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.

 


--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Reply | Threaded
Open this post in threaded view
|

Re: Build for Windows 2012 R2

Bossle, Jody

Michael,

 

Thanks for the information and I have been able to make progress using the VS2015 x64 command prompts.  Unfortunately, I am running into a new error which is captured in a OpenSSL developer thread (see below), but a solution was never posted.  Any additional ideas?

 

http://openssl.6102.n7.nabble.com/Hypothesis-to-explain-quot-error-A2088-END-directive-required-at-end-of-file-quot-td42328.html

 

cid:image001.png@01D1331E.96FD6780

 

Joseph A. Bossle III, “Jody”

Sr. Technical Consultant / Global Information Technology

Baxter International Inc.

One Baxter Parkway / Deerfield, Illinois 60015

T 224.270.3563  /  M 630.650.9413

[hidden email]

 

From: openssl-users [mailto:[hidden email]] On Behalf Of Michael Wojcik
Sent: Monday, April 25, 2016 10:23 AM
To: [hidden email]
Subject: Re: [openssl-users] Build for Windows 2012 R2

 

[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 [[hidden email]] On Behalf Of Bossle, Jody
Sent: Monday, April 25, 2016 08:02
To: [hidden email]
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.

 


--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Reply | Threaded
Open this post in threaded view
|

Re: Build for Windows 2012 R2

Michael Wojcik

I don't know why that message wasn't answered, because it's a well-known issue. I would have mentioned it in my previous note but it slipped my mind.

 

You get that error when you try to use the Microsoft assembler (ml.exe or ml64.exe). For OpenSSL on Windows, you now must use nasm, which is an open-source assembler. You can get it at www.nasm.us. Just download it, install it (which I think is just unzipping an archive), and put it in the path.

 

Michael Wojcik
Technology Specialist, Micro Focus

 

 

From: openssl-users [mailto:[hidden email]] On Behalf Of Bossle, Jody
Sent: Monday, April 25, 2016 22:20
To: [hidden email]
Subject: Re: [openssl-users] Build for Windows 2012 R2

 

Michael,

 

Thanks for the information and I have been able to make progress using the VS2015 x64 command prompts.  Unfortunately, I am running into a new error which is captured in a OpenSSL developer thread (see below), but a solution was never posted.  Any additional ideas?

 

http://openssl.6102.n7.nabble.com/Hypothesis-to-explain-quot-error-A2088-END-directive-required-at-end-of-file-quot-td42328.html

 

 


--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users