-Building OpenSSL under Win32.
-
-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.
-See the end of this file for Eric's original comments.
-
-Note: the default Win32 environment is to leave out any Windows NT specific
-features: (currently only BIO_s_log()) if you want NT specific features see
-the "Tweaks" section later.
-
-You will need perl for Win32 (which can be got from various sources) and Visual
-C++.
-
-If you are compiling from a tarball or a CVS snapshot then the Win32 files may
-well be not up to date. This may mean that some "tweaking" is required to get
-it all to work. See the trouble shooting section later on for if (when?) it
-goes wrong.
-
-Firstly you should run Configure:
-
-perl Configure VC-WIN32
-
-Then rebuild the Win32 Makefiles and friends:
-
-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 stands.
-
-then from the VC++ environment at a prompt do:
-
-nmake -f ms\ntdll.mak
-
-you may get a warning about too many rules but if all is well it should all
-compile and you will have some DLLs and executables in out32dll. If you want
-to try the tests then cd to out32dll and run ..\ms\test
-
-Troubleshooting.
-
-Since the Win32 build is only occasionally tested it may not always compile
-cleanly.
-
-If you get an error about functions not having numbers assigned when you
-run ms\do_ms then this means the Win32 ordinal files are not up to date. You
-can do:
-
-perl util\mkdef.pl crypto ssl update
-
-then ms\do_ms should not give a warning any more. However the numbers that get
-assigned by this technique may not match those that eventually get 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.
-
-In this latter case check out the header file to see if the function is defined
-in the header file: it should be defined twice: once with ANSI prototypes and
-once without. If its missing from the non ASNI section then add an entry for
-it: check that ms\do_ms now reports missing numbers and update the numbers as
-above.
-
-If you get warnings in the code then the compilation will halt.
-
-The default Makefile for Win32 halts whenever any warnings occur. Since VC++
-has its own ideas about warnings which don't always match up to other
-environments this can happen. The best fix is to edit the file with the warning
-in and fix it. Alternatively you can turn off the halt on warnings by editing
-the CFLAG line in the Makefile and deleting the /WX option.
-
-You might get compilation errors. Again you will have to fix these or
-report them.
-
-One final comment about compiling applications linked to the OpenSSL library.
-If you don't use the multithreaded DLL runtime library (/MD option) your
-program will almost certainly crash: see the original SSLeay description below
-for more details.
-
-Tweaks.
-
-There are various changes you can make to the Win32 compile environment. If you
-have the MASM assembler 'ml' then you can try the assembly language code. To
-do this remove the 'no-asm' part from do_ms.bat. You can also add 'debug' here
-to make a debugging version of the library.
-
-If you want to enable the NT specific features of OpenSSL (currently only
-the logging BIO) follow the instructions above but call the batch file
-do_nt.bat instead of do_ms.bat.
-
-You can also build a static version of the library using the Makefile ms\nt.mak
-
---------------------------------------------------------------------------------
-The orignal Windows build instructions from SSLeay follow. Note: some of this
-may be out of date and no longer applicable
---------------------------------------------------------------------------------
-
-The Microsoft World.
-
-The good news, to build SSLeay for the Microsft World
-
-Windows 3.1 DLL's
-perl Configure VC-WIN16
-nmake -f ms\w31dll.mak
-
-Windows NT/95 DLL's
-perl Configure VC-WIN32
-nmake -f ms\ntdll.mak
-
-Now the bad news
-All builds were done using Microsofts Visual C++ 1.52c and [45].x.
-If you are a borland person, you are probably going to have to help me
-finish the stuff in util/pl/BC*pl
-
-All builds were made under Windows NT - this means long filenames, so
-you may have problems under Windows 3.1 but probably not under 95.
-
-Because file pointers don't work in DLL's under Windows 3.1 (well at
-least stdin/stdout don't and I don't like having to differentiate
-between these and other file pointers), I now use the BIO file-pointer
-module, which needs to be linked into your application. You can either
-use the memory buffer BIO for IO, or compile bss_file.c into your
-application, it is in the apps directory and is just a copy of
-crypto/buffer/bss_file.c with #define APPS_WIN16 added.
-I have not yet automated the makefile to automatically copy it into 'out'
-for a win 3.1 build....
-
-All callbacks passed into SSLeay for Windows 3.1 need to be of type
-_far _loadds.
-
-I don't support building with the pascal calling convention.
-
-The DLL and static builds are large memory model.
-
-To build static libraries for NT/95 or win 3.1
-
-perl util/mk1mf.pl VC-WIN32 > mf-stat.nt
-perl util/mk1mf.pl VC-WIN16 > mf-stat.w31
-for DLL's
-perl util/mk1mf.pl dll VC-WIN32 > mf-dll.nt
-perl util/mk1mf.pl dll VC-WIN16 > mf-dll.w31
-
-Again you will notice that if you dont have perl, you cannot do this.
-
-Now the next importaint issue. Running Configure!
-I have small assember code files for critical big number library operation
-in crypto/bn/asm. There is, asm code, object files and uuencode
-object files. They are
-x86nt32.asm - 32bit flat memory model assember - suitable Win32
-x86w16.asm - 16bit assember - used in the msdos build.
-x86w32.asm - 32bit assember, win 3.1 segments, used for win16 build.
-
-If you feel compelled to build the 16bit maths routines in the windows 3.1
-build,
-perl Configure VC-W31-16
-perl util/mk1mf.pl dll VC-W31-16 > mf-dll.w31
-
-If you hate assember and don't want anything to do with it,
-perl util/mk1mf.pl no-asm VC-WIN16 > mf-dll.w31
-will work for any of the makefile generations.
-
-There are more options to mk1mf.pl but these all leave the temporary
-files in 'tmp' and the output files in 'out' by default.
-
-The NT build is done for console mode.
-
-The Windows 3.1 version of SSLeay uses quickwin, the interface is ugly
-but it is better than nothing. If you want ugly, try doing anything
-that involves getting a password. I decided to be ugly instead of
-echoing characters. For Windows 3.1 I would just sugest using the
-msdos version of the ssleay application for command line work.
-The QuickWin build is primarily for testing.
-
-For both NT and Windows 3.1, I have not written the code so that
-s_client, s_server can take input from the keyboard. You can happily
-start applications up in separate windows, watch them handshake, and then sit
-there for-ever. I have not had the time to get this working, and I've
-been able to test things from a unix box to the NT box :-).
-Try running ssleay s_server on the windows box
-(with either -cert ../apps/server.pem -www)
-and run ssleay s_time from another window.
-This often stuffs up on Windows 3.1, but I'm not worried since this is
-probably a problem with my demo applications, not the libraries.
-
-After a build of one of the version of microsoft SSLeay,
-'cd ms' and then run 'test'. This should check everything out and
-even does a trial run of generating certificates.
-'test.bat' requires that perl be install, you be in the ms directory
-(not the test directory, thats for unix so stay out :-) and that the
-build output directory be ../out
-
-On a last note, you will probably get division by zero errors and
-stuff after a build. This is due to your own inability to follow
-instructions :-).
-
-The reasons for the problem is probably one of the following.
-
-1) You did not run Configure. This is critical for windows 3.1 when
- using assember. The values in crypto/bn/bn.h must match the
- ones requred for the assember code. (remember that if you
- edit crypto/bn/bn.h by hand, it will be clobered the next time
- you run Configure by the contents of crypto/bn/bn.org).
- SSLeay version -o will list the compile options.
- For VC-WIN32 you need bn(64,32) or bn(32,32)
- For VC-W31-32/VC-WIN16 you need bn(32,32)
- For VC-W31-16 you need bn(32,16) or bn(16,16)
- For VC-MSDOS you need bn(32,16) or bn(16,16).
-
- The first number will be 2 times bigger than the second if
- BN_LLONG is defined in bn.h and the size of the second number
- depends on the 'bits' defined at the start of bn.h. Have a
- look, it's all reasonably clear.
- If you want to start messing with 8 bit builds and things like
- that, build without the assember by re-generating a makefile
- via 'perl util/mk1mf.pl no-asm'.
-2) You tried to build under MS-DOS or Windows 3.1 using the /G3
- option. Don't. It is buggy (thats why you just got that
- error) and unless you want to work out which optimising flag
- to turn off, I'm not going to help you :-). I also noticed
- that code often ran slower when compiled with /G3.
-3) Under NT/95, malloc goes stupid. You are probably linking with
- the wrong library, there are problems if you mix the threaded
- and non-threaded libraries (due to the DLL being staticly
- linked with one and the applicaion using another.
-
-Well hopefully thats most of the MS issues handled, see you in ssl-users :-).
-
-eric 30-Aug-1996
-
-SSLeay 0.6.5
-For Windows 95/NT, add CRYPTO_malloc_init() to your program before any
-calls to the SSLeay libraries. This function will insert callbacks so that
-the SSLeay libraries will use the same malloc(), free() and realloc() as
-your application so 'problem 3)' mentioned above will go away.
-
-There is now DES assember for Windows NT/95. The file is
-crypto/des/asm/win32.asm and replaces crypto/des/des_enc.c in the build.
-
-There is also Blowfish assember for Windows NT/95. The file is
-crypto/bf/asm/win32.asm and replaces crypto/bf/bf_enc.c in the build.
-
-eric 25-Jun-1997
-
+ \r
+ INSTALLATION ON THE WIN32 PLATFORM\r
+ ----------------------------------\r
+\r
+ [Instructions for building for Windows CE can be found in INSTALL.WCE]\r
+\r
+ Heres a few comments about building OpenSSL in Windows environments. Most\r
+ of this is tested on Win32 but it may also work in Win 3.1 with some\r
+ modification.\r
+\r
+ You need Perl for Win32. Unless you will build on Cygwin, you will need\r
+ ActiveState Perl, available from http://www.activestate.com/ActivePerl.\r
+\r
+ and one of the following C compilers:\r
+\r
+ * Visual C++\r
+ * Borland C\r
+ * GNU C (Cygwin or MinGW)\r
+\r
+ If you are compiling from a tarball or a CVS snapshot then the Win32 files\r
+ may well be not up to date. This may mean that some "tweaking" is required to\r
+ get it all to work. See the trouble shooting section later on for if (when?)\r
+ it goes wrong.\r
+\r
+ Visual C++\r
+ ----------\r
+\r
+ If you want to compile in the assembly language routines with Visual C++ then\r
+ you will need an assembler. This is worth doing because it will result in\r
+ faster code: for example it will typically result in a 2 times speedup in the\r
+ RSA routines. Currently the following assemblers are supported:\r
+\r
+ * Microsoft MASM (aka "ml")\r
+ * Free Netwide Assembler NASM.\r
+\r
+ MASM is distributed with most versions of VC++. For the versions where it is\r
+ not included in VC++, it is also distributed with some Microsoft DDKs, for\r
+ example the Windows NT 4.0 DDK and the Windows 98 DDK. If you do not have\r
+ either of these DDKs then you can just download the binaries for the Windows\r
+ 98 DDK and extract and rename the two files XXXXXml.exe and XXXXXml.err, to\r
+ ml.exe and ml.err and install somewhere on your PATH. Both DDKs can be\r
+ downloaded from the Microsoft developers site www.msdn.com.\r
+\r
+ NASM is freely available. Version 0.98 was used during testing: other versions\r
+ may also work. It is available from many places, see for example:\r
+ http://www.kernel.org/pub/software/devel/nasm/binaries/win32/\r
+ The NASM binary nasmw.exe needs to be installed anywhere on your PATH.\r
+\r
+ Firstly you should run Configure:\r
+\r
+ > perl Configure VC-WIN32\r
+\r
+ Next you need to build the Makefiles and optionally the assembly language\r
+ files:\r
+\r
+ - If you are using MASM then run:\r
+\r
+ > ms\do_masm\r
+\r
+ - If you are using NASM then run:\r
+\r
+ > ms\do_nasm\r
+\r
+ - If you don't want to use the assembly language files at all then run:\r
+\r
+ > ms\do_ms\r
+\r
+ If you get errors about things not having numbers assigned then check the\r
+ troubleshooting section: you probably won't be able to compile it as it\r
+ stands.\r
+\r
+ Then from the VC++ environment at a prompt do:\r
+\r
+ > nmake -f ms\ntdll.mak\r
+\r
+ If all is well it should compile and you will have some DLLs and executables\r
+ in out32dll. If you want to try the tests then do:\r
+ \r
+ > cd out32dll\r
+ > ..\ms\test\r
+\r
+ Tweaks:\r
+\r
+ There are various changes you can make to the Win32 compile environment. By\r
+ default the library is not compiled with debugging symbols. If you add 'debug'\r
+ to the mk1mf.pl lines in the do_* batch file then debugging symbols will be\r
+ compiled in. Note that mk1mf.pl expects the platform to be the last argument\r
+ on the command line, so 'debug' must appear before that, as all other options.\r
+\r
+ The default Win32 environment is to leave out any Windows NT specific\r
+ features.\r
+\r
+ If you want to enable the NT specific features of OpenSSL (currently only the\r
+ logging BIO) follow the instructions above but call the batch file do_nt.bat\r
+ instead of do_ms.bat.\r
+\r
+ You can also build a static version of the library using the Makefile\r
+ ms\nt.mak\r
+\r
+ Borland C++ builder 5\r
+ ---------------------\r
+\r
+ * Configure for building with Borland Builder:\r
+ > perl Configure BC-32\r
+\r
+ * Create the appropriate makefile\r
+ > ms\do_nasm\r
+\r
+ * Build\r
+ > make -f ms\bcb.mak\r
+\r
+ Borland C++ builder 3 and 4\r
+ ---------------------------\r
+\r
+ * Setup PATH. First must be GNU make then bcb4/bin \r
+\r
+ * Run ms\bcb4.bat\r
+\r
+ * Run make:\r
+ > make -f bcb.mak\r
+\r
+ GNU C (Cygwin)\r
+ --------------\r
+\r
+ Cygwin provides a bash shell and GNU tools environment running\r
+ on NT 4.0, Windows 9x, Windows ME, Windows 2000, and Windows XP.\r
+ Consequently, a make of OpenSSL with Cygwin is closer to a GNU\r
+ bash environment such as Linux than to other the other Win32\r
+ makes.\r
+\r
+ Cygwin implements a Posix/Unix runtime system (cygwin1.dll).\r
+ It is also possible to create Win32 binaries that only use the\r
+ Microsoft C runtime system (msvcrt.dll or crtdll.dll) using\r
+ MinGW. MinGW can be used in the Cygwin development environment\r
+ or in a standalone setup as described in the following section.\r
+\r
+ To build OpenSSL using Cygwin:\r
+\r
+ * Install Cygwin (see http://cygwin.com/)\r
+\r
+ * Install Perl and ensure it is in the path. Both Cygwin perl\r
+ (5.6.1-2 or newer) and ActivePerl work.\r
+\r
+ * Run the Cygwin bash shell\r
+\r
+ * $ tar zxvf openssl-x.x.x.tar.gz\r
+ $ cd openssl-x.x.x\r
+\r
+ To build the Cygwin version of OpenSSL:\r
+\r
+ $ ./config\r
+ [...]\r
+ $ make\r
+ [...]\r
+ $ make test\r
+ $ make install\r
+\r
+ This will create a default install in /usr/local/ssl.\r
+\r
+ To build the MinGW version (native Windows) in Cygwin:\r
+\r
+ $ ./Configure mingw\r
+ [...]\r
+ $ make\r
+ [...]\r
+ $ make test\r
+ $ make install\r
+\r
+ Cygwin Notes:\r
+\r
+ "make test" and normal file operations may fail in directories\r
+ mounted as text (i.e. mount -t c:\somewhere /home) due to Cygwin\r
+ stripping of carriage returns. To avoid this ensure that a binary\r
+ mount is used, e.g. mount -b c:\somewhere /home.\r
+\r
+ "bc" is not provided in older Cygwin distribution. This causes a\r
+ non-fatal error in "make test" but is otherwise harmless. If\r
+ desired and needed, GNU bc can be built with Cygwin without change.\r
+\r
+ GNU C (MinGW)\r
+ -------------\r
+\r
+ * Compiler installation:\r
+\r
+ MinGW is available from http://www.mingw.org. Run the installer and\r
+ set the MinGW bin directory to the PATH in "System Properties" or\r
+ autoexec.bat.\r
+\r
+ * Compile OpenSSL:\r
+\r
+ > ms\mingw32\r
+\r
+ This will create the library and binaries in out. In case any problems\r
+ occur, try\r
+ > ms\mingw32 no-asm\r
+ instead.\r
+\r
+ libcrypto.a and libssl.a are the static libraries. To use the DLLs,\r
+ link with libeay32.a and libssl32.a instead.\r
+\r
+ See troubleshooting if you get error messages about functions not having\r
+ a number assigned.\r
+\r
+ * You can now try the tests:\r
+\r
+ > cd out\r
+ > ..\ms\test\r
+\r
+\r
+ Installation\r
+ ------------\r
+\r
+ If you used the Cygwin procedure above, you have already installed and\r
+ can skip this section. For all other procedures, there's currently no real\r
+ installation procedure for Win32. There are, however, some suggestions:\r
+\r
+ - do nothing. The include files are found in the inc32/ subdirectory,\r
+ all binaries are found in out32dll/ or out32/ depending if you built\r
+ dynamic or static libraries.\r
+\r
+ - do as is written in INSTALL.Win32 that comes with modssl:\r
+\r
+ $ md c:\openssl \r
+ $ md c:\openssl\bin\r
+ $ md c:\openssl\lib\r
+ $ md c:\openssl\include\r
+ $ md c:\openssl\include\openssl\r
+ $ copy /b inc32\* c:\openssl\include\openssl\r
+ $ copy /b out32dll\ssleay32.lib c:\openssl\lib\r
+ $ copy /b out32dll\libeay32.lib c:\openssl\lib\r
+ $ copy /b out32dll\ssleay32.dll c:\openssl\bin\r
+ $ copy /b out32dll\libeay32.dll c:\openssl\bin\r
+ $ copy /b out32dll\openssl.exe c:\openssl\bin\r
+\r
+ Of course, you can choose another device than c:. C: is used here\r
+ because that's usually the first (and often only) harddisk device.\r
+ Note: in the modssl INSTALL.Win32, p: is used rather than c:.\r
+\r
+\r
+ Troubleshooting\r
+ ---------------\r
+\r
+ Since the Win32 build is only occasionally tested it may not always compile\r
+ cleanly. If you get an error about functions not having numbers assigned\r
+ when you run ms\do_ms then this means the Win32 ordinal files are not up to\r
+ date. You can do:\r
+\r
+ > perl util\mkdef.pl crypto ssl update\r
+\r
+ then ms\do_XXX should not give a warning any more. However the numbers that\r
+ get assigned by this technique may not match those that eventually get\r
+ assigned in the CVS tree: so anything linked against this version of the\r
+ library may need to be recompiled.\r
+\r
+ If you get errors about unresolved symbols there are several possible\r
+ causes.\r
+\r
+ If this happens when the DLL is being linked and you have disabled some\r
+ ciphers then it is possible the DEF file generator hasn't removed all\r
+ the disabled symbols: the easiest solution is to edit the DEF files manually\r
+ to delete them. The DEF files are ms\libeay32.def ms\ssleay32.def.\r
+\r
+ Another cause is if you missed or ignored the errors about missing numbers\r
+ mentioned above.\r
+\r
+ If you get warnings in the code then the compilation will halt.\r
+\r
+ The default Makefile for Win32 halts whenever any warnings occur. Since VC++\r
+ has its own ideas about warnings which don't always match up to other\r
+ environments this can happen. The best fix is to edit the file with the\r
+ warning in and fix it. Alternatively you can turn off the halt on warnings by\r
+ editing the CFLAG line in the Makefile and deleting the /WX option.\r
+\r
+ You might get compilation errors. Again you will have to fix these or report\r
+ them.\r
+\r
+ One final comment about compiling applications linked to the OpenSSL library.\r
+ If you don't use the multithreaded DLL runtime library (/MD option) your\r
+ program will almost certainly crash because malloc gets confused -- the\r
+ OpenSSL DLLs are statically linked to one version, the application must\r
+ not use a different one. You might be able to work around such problems\r
+ by adding CRYPTO_malloc_init() to your program before any calls to the\r
+ OpenSSL libraries: This tells the OpenSSL libraries to use the same\r
+ malloc(), free() and realloc() as the application. However there are many\r
+ standard library functions used by OpenSSL that call malloc() internally\r
+ (e.g. fopen()), and OpenSSL cannot change these; so in general you cannot\r
+ rely on CRYPTO_malloc_init() solving your problem, and you should\r
+ consistently use the multithreaded library.\r
projects / openssl.git / blobdiff