diff options
| author | Matt Caswell <matt@openssl.org> | 2016-01-14 20:16:40 +0000 |
|---|---|---|
| committer | Matt Caswell <matt@openssl.org> | 2016-01-15 11:01:00 +0000 |
| commit | 46bf69b5934d45f9e00b962f26cf15b8fe8a1e56 (patch) | |
| tree | 329248ab7af001ccfbb52b50df104e01c719d31a | |
| parent | 1de8e63f86e1f1a60961489c47be55bb5f03e8d7 (diff) | |
Rename INSTALL.W32 to INSTALL.WIN
Also remove the INSTALL.W64 file. Next commit will update INSTALL.WIN to
cover both.
Reviewed-by: Richard Levitte <levitte@openssl.org>
| -rw-r--r-- | INSTALL.W64 | 66 | ||||
| -rw-r--r-- | INSTALL.WIN (renamed from INSTALL.W32) | 0 |
2 files changed, 0 insertions, 66 deletions
diff --git a/INSTALL.W64 b/INSTALL.W64 deleted file mode 100644 index 9fa7a19205..0000000000 --- a/INSTALL.W64 +++ /dev/null @@ -1,66 +0,0 @@ - - INSTALLATION ON THE WIN64 PLATFORM - ---------------------------------- - - Caveat lector - ------------- - - As of moment of this writing Win64 support is classified "initial" - for the following reasons. - - - No assembler modules are engaged upon initial 0.9.8 release. - - API might change within 0.9.8 life-span, *but* in a manner which - doesn't break backward binary compatibility. Or in other words, - application programs compiled with initial 0.9.8 headers will - be expected to work with future minor release .DLL without need - to re-compile, even if future minor release features modified API. - - Above mentioned API modifications have everything to do with - elimination of a number of limitations, which are normally - considered inherent to 32-bit platforms. Which in turn is why they - are treated as limitations on 64-bit platform such as Win64:-) - The current list comprises [but not necessarily limited to]: - - - null-terminated strings may not be longer than 2G-1 bytes, - longer strings are treated as zero-length; - - dynamically and *internally* allocated chunks can't be larger - than 2G-1 bytes; - - inability to encrypt/decrypt chunks of data larger than 4GB - [it's possibly to *hash* chunks of arbitrary size through]; - - Neither of these is actually big deal and hardly encountered - in real-life applications. - - Compiling procedure - ------------------- - - You will need Perl. You can run under Cygwin or you can download - ActiveState Perl from http://www.activestate.com/ActivePerl. - - You will need Microsoft Platform SDK, available for download at - http://www.microsoft.com/msdownload/platformsdk/sdkupdate/. As per - April 2005 Platform SDK is equipped with Win64 compilers, as well - as assemblers, but it might change in the future. - - To build for Win64/x64: - - > perl Configure VC-WIN64A - > ms\do_win64a - > nmake -f ms\ntdll.mak - > cd out32dll - > ..\ms\test - - To build for Win64/IA64: - - > perl Configure VC-WIN64I - > ms\do_win64i - > nmake -f ms\ntdll.mak - > cd out32dll - > ..\ms\test - - Naturally test-suite itself has to be executed on the target platform. - - Installation - ------------ - - TBD, for now see INSTALL.W32. - diff --git a/INSTALL.W32 b/INSTALL.WIN index 80e538273e..80e538273e 100644 --- a/INSTALL.W32 +++ b/INSTALL.WIN |