X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=INSTALL.W32;h=8ec2f9f82021c94ebf0350d4102c5010e2d42046;hp=9122410404a4aed525986dc767dc34ba813660f4;hb=6c5d4168ff810540bb47c999c1ceff28190911e5;hpb=5c00879ef093f9fb8ed2a9b58993e90401ec7b50 diff --git a/INSTALL.W32 b/INSTALL.W32 index 9122410404..8ec2f9f820 100644 --- a/INSTALL.W32 +++ b/INSTALL.W32 @@ -1,83 +1,104 @@ -Building OpenSSL under Win32. + + 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 modification. -See the end of this file for Eric's original comments. + 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. -You will need perl for Win32 (which can be got from various sources) and Visual -C++. + 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. -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. + You will need perl for Win32 (which can be got from various sources) and + Visual C++. -Firstly you should run Configure: + 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. -perl Configure VC-WIN32 + Firstly you should run Configure: -Then rebuild the Win32 Makefiles and friends: + > perl Configure VC-WIN32 -ms\do_ms + Then rebuild the Win32 Makefiles and friends: -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. + > ms\do_ms -then from the VC++ environment at a prompt do: + 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. -nmake -f ms\ntdll.mak + Then from the VC++ environment at a prompt do: + + > nmake -f ms\ntdll.mak + + 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 -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. + Troubleshooting + --------------- -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: -Since the Win32 build is only occasionally tested it may not always compile -cleanly. + > perl util\mkdef.pl crypto ssl update -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: + 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. -perl util\mkdef.pl crypto ssl update + 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. -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 you anything linked against this version of the library -may need to be recompiled. + 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 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 warnings in the code then the compilation will halt. -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. + 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. -If you get warnings in the code then the compilation will halt. + You might get compilation errors. Again you will have to fix these or report + them. -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. + 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. -Finally you might get compilation errors. Again you will have to fix these or -report them. + Tweaks + ------ -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. -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. + 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 + 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 orignal Windows build instructions from SSLeay follow. +Note: some of this may be out of date and no longer applicable -------------------------------------------------------------------------------- The Microsoft World.