From df8dae1df4a03cdf61e87c605ebacf8aa6064890 Mon Sep 17 00:00:00 2001 From: "Dr. Stephen Henson" Date: Mon, 7 Nov 2005 00:35:22 +0000 Subject: [PATCH] Update docs. --- INSTALL.W32 | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/INSTALL.W32 b/INSTALL.W32 index a4b6700e2e..3dd7832f4e 100644 --- a/INSTALL.W32 +++ b/INSTALL.W32 @@ -49,7 +49,9 @@ Firstly you should run Configure: - > perl Configure VC-WIN32 + > perl Configure VC-WIN32 --prefix=c:/some/openssl/dir + +Where the prefix argument specifies where OpenSSL will be installed to. Next you need to build the Makefiles and optionally the assembly language files: @@ -77,8 +79,12 @@ If all is well it should compile and you will have some DLLs and executables in out32dll. If you want to try the tests then do: - > cd out32dll - > ..\ms\test + > nmake -f ms\ntdll.mak test + + +To install OpenSSL to the specified location do: + +> nmake -f ms\ntdll.mak install Tweaks: @@ -88,6 +94,12 @@ compiled in. Note that mk1mf.pl expects the platform to be the last argument on the command line, so 'debug' must appear before that, as all other options. + + By default in 0.9.8 OpenSSL will compile builtin ENGINES into the libeay32.dll + shared library. If you specify the "no-static-engine" option on the command + line to Configure the shared library build (ms\ntdll.mak) will compile the + engines as separate DLLs. + The default Win32 environment is to leave out any Windows NT specific features. @@ -98,6 +110,8 @@ You can also build a static version of the library using the Makefile ms\nt.mak + + Borland C++ builder 5 --------------------- -- 2.25.1