INSTALL.W64 2.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374
  1. INSTALLATION ON THE WIN64 PLATFORM
  2. ----------------------------------
  3. Caveat lector
  4. -------------
  5. As of moment of this writing Win64 support is classified "initial"
  6. for the following reasons.
  7. - No assembler modules are engaged upon initial 0.9.8 release.
  8. - API might change within 0.9.8 life-span, *but* in a manner which
  9. doesn't break backward binary compatibility. Or in other words,
  10. application programs compiled with initial 0.9.8 headers will
  11. be expected to work with future minor release .DLL without need
  12. to re-compile, even if future minor release features modified API.
  13. - Above mentioned API modifications have everything to do with
  14. elimination of a number of limitations, which are normally
  15. considered inherent to 32-bit platforms. Which in turn is why they
  16. are treated as limitations on 64-bit platform such as Win64:-)
  17. The current list comprises [but not necessarily limited to]:
  18. - null-terminated strings may not be longer than 2G-1 bytes,
  19. longer strings are treated as zero-length;
  20. - dynamically and *internally* allocated chunks can't be larger
  21. than 2G-1 bytes;
  22. - inability to encrypt/decrypt chunks of data larger than 4GB
  23. [it's possibly to *hash* chunks of arbitrary size through];
  24. Neither of these is actually big deal and hardly encountered
  25. in real-life applications.
  26. ### Default install and config paths
  27. ./Configure defaults to '/usr/local/ssl' as installation top. This is
  28. suitable for Unix, but not for Windows, where this usually is a world
  29. writable directory and therefore accessible for change by untrusted users.
  30. It is therefore recommended to set your own --prefix or --openssldir to
  31. some location that is not world writeable (see the example above)
  32. Compiling procedure
  33. -------------------
  34. You will need Perl. You can run under Cygwin or you can download
  35. ActiveState Perl from http://www.activestate.com/ActivePerl.
  36. You will need Microsoft Platform SDK, available for download at
  37. http://www.microsoft.com/msdownload/platformsdk/sdkupdate/. As per
  38. April 2005 Platform SDK is equipped with Win64 compilers, as well
  39. as assemblers, but it might change in the future.
  40. To build for Win64/x64:
  41. > perl Configure VC-WIN64A --prefix=c:\some\openssl\dir
  42. > ms\do_win64a
  43. > nmake -f ms\ntdll.mak
  44. > cd out32dll
  45. > ..\ms\test
  46. To build for Win64/IA64:
  47. > perl Configure VC-WIN64I --prefix=c:\some\openssl\dir
  48. > ms\do_win64i
  49. > nmake -f ms\ntdll.mak
  50. > cd out32dll
  51. > ..\ms\test
  52. Naturally test-suite itself has to be executed on the target platform.
  53. Installation
  54. ------------
  55. TBD, for now see INSTALL.W32.