INSTALL.WCE 2.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374
  1. INSTALLATION FOR THE WINDOWS CE PLATFORM
  2. ----------------------------------------
  3. Building OpenSSL for Windows CE requires the following external tools:
  4. * Microsoft eMbedded Visual C++ 3.0
  5. * wcecompat compatibility library (www.essemer.com.au)
  6. * Optionally ceutils for running automated tests (www.essemer.com.au)
  7. You also need Perl for Win32. You will need ActiveState Perl, available
  8. from http://www.activestate.com/ActivePerl.
  9. Windows CE support in OpenSSL relies on wcecompat and therefore it's
  10. appropriate to check http://www.essemer.com.au/windowsce/ for updates in
  11. case of compilation problems. As for the moment of this writing version
  12. 1.1 is available and actually required for WCE 4.2 and newer platforms.
  13. All Windows CE specific issues should be directed to www.essemer.com.au.
  14. The C Runtime Library implementation for Windows CE that is included with
  15. Microsoft eMbedded Visual C++ 3.0 is incomplete and in some places
  16. incorrect. wcecompat plugs the holes and tries to bring the Windows CE
  17. CRT to a level that is more compatible with ANSI C. wcecompat goes further
  18. and provides low-level IO and stream IO support for stdin/stdout/stderr
  19. (which Windows CE does not provide). This IO functionality is not needed
  20. by the OpenSSL library itself but is used for the tests and openssl.exe.
  21. More information is available at www.essemer.com.au.
  22. Building
  23. --------
  24. Setup the eMbedded Visual C++ environment. There are batch files for doing
  25. this installed with eVC++. For an ARM processor, for example, execute:
  26. > "C:\Program Files\Microsoft eMbedded Tools\EVC\WCE300\BIN\WCEARM.BAT"
  27. Next indicate where wcecompat is located:
  28. > set WCECOMPAT=C:\wcecompat
  29. Next you should run Configure:
  30. > perl Configure VC-CE
  31. Next you need to build the Makefiles:
  32. > ms\do_ms
  33. If you get errors about things not having numbers assigned then check the
  34. troubleshooting section in INSTALL.W32: you probably won't be able to compile
  35. it as it stands.
  36. Then from the VC++ environment at a prompt do:
  37. - to build static libraries:
  38. > nmake -f ms\ce.mak
  39. - or to build DLLs:
  40. > nmake -f ms\cedll.mak
  41. If all is well it should compile and you will have some static libraries and
  42. executables in out32, or some DLLs and executables in out32dll. If you want
  43. to try the tests then make sure the ceutils are in the path and do:
  44. > cd out32
  45. > ..\ms\testce
  46. This will copy each of the test programs to the Windows CE device and execute
  47. them, displaying the output of the tests on this computer. The output should
  48. look similar to the output produced by running the tests for a regular Windows
  49. build.