X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=INSTALL.W32;h=8a875cf0beff027a656411da651690cdedc0538f;hp=618a5107bb85ab0c18e37c16b37d2c20e8fd66c0;hb=f70ddce761ea237c27c933303ad7935c102c5eb3;hpb=889a54c4671acbf59adc399831525e50a5902580 diff --git a/INSTALL.W32 b/INSTALL.W32 index 618a5107bb..8a875cf0be 100644 --- a/INSTALL.W32 +++ b/INSTALL.W32 @@ -2,16 +2,21 @@ INSTALLATION ON THE WIN32 PLATFORM ---------------------------------- - Heres a few comments about building OpenSSL in Windows environments. Most of - this is tested on Win32 but it may also work in Win 3.1 with some + [Instructions for building for Windows CE can be found in INSTALL.WCE] + + Heres a few comments about building OpenSSL in Windows environments. Most + of this is tested on Win32 but it may also work in Win 3.1 with some modification. - You need Perl for Win32 (available from http://www.activestate.com/ActivePerl) + You need Perl for Win32. Unless you will build on Cygwin, you will need + ActiveState Perl, available from http://www.activestate.com/ActivePerl. + For Cygwin users, there's more info in the Cygwin section. + and one of the following C compilers: * Visual C++ * Borland C - * GNU C (Mingw32 or Cygwin32) + * GNU C (Mingw32 or Cygwin) If you want to compile in the assembly language routines with Visual C++ then you will need an assembler. This is worth doing because it will result in @@ -78,8 +83,9 @@ There are various changes you can make to the Win32 compile environment. By default the library is not compiled with debugging symbols. If you add 'debug' - to the mk1mk.pl lines in the do_* batch file then debugging symbols will be - compiled in. + to the mk1mf.pl lines in the do_* batch file then debugging symbols will be + 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. The default Win32 environment is to leave out any Windows NT specific features. @@ -91,6 +97,18 @@ You can also build a static version of the library using the Makefile ms\nt.mak + Borland C++ builder 5 + --------------------- + + * Configure for building with Borland Builder: + > perl Configure BC-32 + + * Create the appropriate makefile + > ms\do_nasm + + * Build + > make -f ms\bcb.mak + Borland C++ builder 3 and 4 --------------------------- @@ -109,10 +127,10 @@ * Compiler installation: Mingw32 is available from . GNU make is at - . Install both of them in C:\egcs-1.1.2 and run - C:\egcs-1.1.2\mingw32.bat to set the PATH. + gnu-win32/mingw32/gcc-2.95.2/gcc-2.95.2-msvcrt.exe>. Extract it + to a directory such as C:\gcc-2.95.2 and add c:\gcc-2.95.2\bin to + the PATH environment variable in "System Properties"; or edit and + run C:\gcc-2.95.2\mingw32.bat to set the PATH. * Compile OpenSSL: @@ -134,29 +152,30 @@ > cd out > ..\ms\test - GNU C (CygWin32) - --------------- + GNU C (Cygwin) + -------------- - CygWin32 provides a bash shell and GNU tools environment running on - NT 4.0, Windows 9x and Windows 2000. Consequently, a make of OpenSSL - with CygWin is closer to a GNU bash environment such as Linux rather - than other W32 makes that are based on a single makefile approach. - CygWin32 implements Posix/Unix calls through cygwin1.dll, and is - contrasted to Mingw32 which links dynamically to msvcrt.dll or - crtdll.dll. + Cygwin provides a bash shell and GNU tools environment running + on NT 4.0, Windows 9x, Windows ME, Windows 2000, and Windows XP. + Consequently, a make of OpenSSL with Cygwin is closer to a GNU + bash environment such as Linux than to other W32 makes which are + based on a single makefile approach. Cygwin implements Posix/Unix + calls through cygwin1.dll, and is contrasted to Mingw32 which links + dynamically to msvcrt.dll or crtdll.dll. - To build OpenSSL using CygWin32: + To build OpenSSL using Cygwin: - * Install CygWin32 (see http://sourceware.cygnus.com/cygwin) + * Install Cygwin (see http://cygwin.com/) - * Install Perl and ensure it is in the path (recent Cygwin perl or + * Install Perl and ensure it is in the path (recent Cygwin perl + (version 5.6.1-2 of the latter has been reported to work) or ActivePerl) - * Run the CygWin bash shell + * Run the Cygwin bash shell * $ tar zxvf openssl-x.x.x.tar.gz $ cd openssl-x.x.x - $ ./Configure no-threads CygWin32 + $ ./config [...] $ make [...] @@ -165,27 +184,24 @@ This will create a default install in /usr/local/ssl. - CygWin32 Notes: + Cygwin Notes: "make test" and normal file operations may fail in directories - mounted as text (i.e. mount -t c:\somewhere /home) due to CygWin + mounted as text (i.e. mount -t c:\somewhere /home) due to Cygwin stripping of carriage returns. To avoid this ensure that a binary mount is used, e.g. mount -b c:\somewhere /home. - As of version 1.1.1 CygWin32 is relatively unstable in its handling - of cr/lf issues. These make procedures succeeded with versions 1.1 and - the snapshot 20000524 (Slow!). - - "bc" is not provided in the CygWin32 distribution. This causes a + "bc" is not provided in older Cygwin distribution. This causes a non-fatal error in "make test" but is otherwise harmless. If - desired, GNU bc can be built with CygWin32 without change. + desired and needed, GNU bc can be built with Cygwin without change. Installation ------------ - There's currently no real installation procedure for Win32. There are, - however, some suggestions: + If you used the Cygwin procedure above, you have already installed and + can skip this section. For all other procedures, there's currently no real + installation procedure for Win32. There are, however, some suggestions: - do nothing. The include files are found in the inc32/ subdirectory, all binaries are found in out32dll/ or out32/ depending if you built @@ -257,5 +273,5 @@ malloc(), free() and realloc() as the application. However there are many standard library functions used by OpenSSL that call malloc() internally (e.g. fopen()), and OpenSSL cannot change these; so in general you cannot - rely on CYRPTO_malloc_init() solving your problem, and you should + rely on CRYPTO_malloc_init() solving your problem, and you should consistently use the multithreaded library.