X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=blobdiff_plain;f=INSTALL.W32;h=0d71a46bdf4f20bd938aab4f7885ac2acf09ad9f;hp=6d09a223109961141d3aea65c984531ce9007bfd;hb=f1e6643751d1f6a30bd63c4dab7c0a10a9bc9ec5;hpb=657e60fa00ddde3618600d6306be913214d30457 diff --git a/INSTALL.W32 b/INSTALL.W32 index 6d09a22310..0d71a46bdf 100644 --- a/INSTALL.W32 +++ b/INSTALL.W32 @@ -2,16 +2,19 @@ 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 + 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 @@ -21,10 +24,12 @@ * Microsoft MASM (aka "ml") * Free Netwide Assembler NASM. - MASM was I believe distributed in the past with VC++ and it is also part of - the MSDN SDKs. It is no longer distributed as part of VC++ and can be hard - to get hold of. It can be purchased: see Microsoft's site for details at: - http://www.microsoft.com/ + MASM was at one point distributed with VC++. It is now distributed with some + Microsoft DDKs, for example the Windows NT 4.0 DDK and the Windows 98 DDK. If + you do not have either of these DDKs then you can just download the binaries + for the Windows 98 DDK and extract and rename the two files XXXXXml.exe and + XXXXXml.err, to ml.exe and ml.err and install somewhere on your PATH. Both + DDKs can be downloaded from the Microsoft developers site www.msdn.com. NASM is freely available. Version 0.98 was used during testing: other versions may also work. It is available from many places, see for example: @@ -59,7 +64,7 @@ > ms\do_ms If you get errors about things not having numbers assigned then check the - troubleshooting section: you probably wont be able to compile it as it + troubleshooting section: you probably won't be able to compile it as it stands. Then from the VC++ environment at a prompt do: @@ -76,7 +81,7 @@ 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 + to the mk1mf.pl lines in the do_* batch file then debugging symbols will be compiled in. The default Win32 environment is to leave out any Windows NT specific @@ -106,18 +111,20 @@ * Compiler installation: - Mingw32 is available from . GNU make is at + 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. * Compile OpenSSL: - > perl Configure Mingw32 - > ms\mw.bat + > ms\mingw32 - This will create the library and binaries in out. + This will create the library and binaries in out. In case any problems + occur, try + > ms\mingw32 no-asm + instead. libcrypto.a and libssl.a are the static libraries. To use the DLLs, link with libeay32.a and libssl32.a instead. @@ -130,6 +137,84 @@ > cd out > ..\ms\test + GNU C (Cygwin) + -------------- + + Cygwin 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. + 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 Cygwin: + + * Install Cygwin (see http://sourceware.cygnus.com/cygwin) + + * 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 + + * $ tar zxvf openssl-x.x.x.tar.gz + $ cd openssl-x.x.x + $ ./config + [...] + $ make + [...] + $ make test + $ make install + + This will create a default install in /usr/local/ssl. + + 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 + 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 Cygwin 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 Cygwin distribution. This causes a + non-fatal error in "make test" but is otherwise harmless. If + desired, GNU bc can be built with Cygwin without change. + + + Installation + ------------ + + 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 + dynamic or static libraries. + + - do as is written in INSTALL.Win32 that comes with modssl: + + $ md c:\openssl + $ md c:\openssl\bin + $ md c:\openssl\lib + $ md c:\openssl\include + $ md c:\openssl\include\openssl + $ copy /b inc32\* c:\openssl\include\openssl + $ copy /b out32dll\ssleay32.lib c:\openssl\lib + $ copy /b out32dll\libeay32.lib c:\openssl\lib + $ copy /b out32dll\ssleay32.dll c:\openssl\bin + $ copy /b out32dll\libeay32.dll c:\openssl\bin + $ copy /b out32dll\openssl.exe c:\openssl\bin + + Of course, you can choose another device than c:. C: is used here + because that's usually the first (and often only) harddisk device. + Note: in the modssl INSTALL.Win32, p: is used rather than c:. + + Troubleshooting --------------- @@ -145,12 +230,16 @@ assigned in the CVS tree: so anything linked against this version of the library may need to be recompiled. - If you get errors about unresolved externals then this means that either you - didn't read the note above about functions not having numbers assigned or - someone forgot to add a function to the header file. + If you get errors about unresolved symbols there are several possible + causes. + + If this happens when the DLL is being linked and you have disabled some + ciphers then it is possible the DEF file generator hasn't removed all + the disabled symbols: the easiest solution is to edit the DEF files manually + to delete them. The DEF files are ms\libeay32.def ms\ssleay32.def. - In this latter case check out the header file to see if the function is - defined in the header file. + Another cause is if you missed or ignored the errors about missing numbers + mentioned above. If you get warnings in the code then the compilation will halt. @@ -173,5 +262,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.