Build OpenSSL with MS Visual C++ - Revision history

Cjkelly1: Specify to use the 1.0.x tree for CWE

2019-04-06T05:13:55Z

Specify to use the 1.0.x tree for CWE

2018-12-05T22:31:46Z

Changed target from ntdll.mak to nt.dll, so a static library is generated.

2013-07-12T19:37:37Z

Preparation: Add missing note on NASM.

2013-07-12T19:09:50Z

Create the Make files: Typo

2013-07-12T19:07:42Z

Configure Perl: Clarify instructions

2013-07-12T19:06:04Z

Create the Make files: Fix typo

2011-12-24T14:52:32Z

Run the self-tests and "install" the finished products: Wrong DLL name

2011-12-24T13:35:02Z

Create the Make files: typo

2011-12-24T13:32:36Z

Run the self-tests and "install" the finished products: Typo

2011-12-24T13:29:11Z

Check nMake from the command prompt: spacing

@@ Line 7: / Line 7: @@
 You will also need Perl to build the make files. On a Windows machine you should download and install [http://www.activestate.com/ActivePerl ActiveState Perl].
-Download the latest openssl tarball from http://www.openssl.org/source/ and unpack (e.g. using WinRAR) to a convenient location. You will need to run some commands from a command prompt so choose a location that you can navigate to easily from a command prompt.
+Download the latest openssl 1.0.x (1.1.x and later will not work for CWE) tarball from http://www.openssl.org/source/ and unpack (e.g. using WinRAR) to a convenient location. You will need to run some commands from a command prompt so choose a location that you can navigate to easily from a command prompt.
 == Configure Perl ==

@@ Line 39: / Line 39: @@
 Assuming everything is OK you should get a few screenfuls of text and return to the command prompt without errors. Now build the files using the following command:<br>
-<code>nmake -f ms\ntdll.mak</code>
+<code>nmake -f ms\nt.mak</code>
 This may take a few minutes to run depending on your computer speed, but you should see many pages of components being compiled or assembled.
@@ Line 45: / Line 45: @@
 == Run the self-tests and "install" the finished products ==
 Once everything has been built, check it by running the included set of test applications:<br>
-<code>nmake -f ms\ntdll.mak test</code>
+<code>nmake -f ms\nt.mak test</code>
 You will see the test scenarios being run. If these look OK you're ready to export the finished libraries to the destination directory you created earlier and configured in Perl (the instructions in INSTALL.W32  refer to this as "installing OpenSSL"):<br>
-<code>nmake -f ms\ntdll.mak install</code>
+<code>nmake -f ms\nt.mak install</code>
 View the directory and check that it contains the following folder structure:

@@ Line 3: / Line 3: @@
 == Preparation ==
-It is assumed that you already have Visual Studio (or Visual C++) installed.
+It is assumed that you already have Visual Studio (or Visual C++) installed.  You may also need [http://sourceforge.net/projects/nasm Netwide Assembler (NASM)] - Ensure that the folder where nasm.exe is located in in your PATH variable.
 You will also need Perl to build the make files. On a Windows machine you should download and install [http://www.activestate.com/ActivePerl ActiveState Perl].
 Download the latest openssl tarball from http://www.openssl.org/source/ and unpack (e.g. using WinRAR) to a convenient location. You will need to run some commands from a command prompt so choose a location that you can navigate to easily from a command prompt.
 == Configure Perl ==

@@ Line 42: / Line 42: @@
 <code>nmake -f ms\ntdll.mak</code>
-This may take a few minutes to run depending on your computer speed, but you should see many pages of componentes being compiled or assembled.
+This may take a few minutes to run depending on your computer speed, but you should see many pages of components being compiled or assembled.
 == Run the self-tests and "install" the finished products ==

@@ Line 13: / Line 13: @@
 Create a separate, empty folder where you want the finished products to go. Again, make this easy to locate from a command prompt. We now need to tell Perl about this folder.
-Open a command prompt and type the following command, where d:/my/openssl/dir is the name of the folder you just created:<br>
+Open a command prompt, navigate to the folder containing the Open SSL sources and type the following command, where d:/my/openssl/dir is the name of the folder you just created:<br>
 <code>perl Configure VC-WIN32 --prefix=d:/my/openssl/dir</code>
 == Check nMake from the command prompt ==

@@ Line 38: / Line 38: @@
 Now type the following command to build the make files:<br>
-<code>ms\do_masm</code>
+<code>ms\do_nasm</code>
 Assuming everything is OK you should get a few screenfuls of text and return to the command prompt without errors. Now build the files using the following command:<br>

@@ Line 56: / Line 56: @@
     libeay32.dll
     openssl.exe
-    openssl.exe
+    ssleay32.dll
   [include]
     [openssl]

@@ Line 22: / Line 22: @@
 Depending on how Visual Studio/Visual C++ is installed, you may need to set up the compiler to run from the command prompt. Type the following command with no arguments:<br>
-<code>nmake</code>
+<code>nmake</code><br>
 If nmake runs and you get a "fatal error U1001" then the compiler will run from the command prompt. If you get an error message that nmake is not a recognized command then you need to setup the compiler environment variables.
@@ Line 29: / Line 29: @@
 '''Note:''' you must do this from the command prompt you are going to work in: Do '''not''' try to double click on the .bat file in Windows Explorer or use a different command window - it will not work!
 == Create the Make files ==