INSTALL.WCE 2.4 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  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. All Windows CE specific
  10. issues should be directed to www.essemer.com.au.
  11. The C Runtime Library implementation for Windows CE that is included with
  12. Microsoft eMbedded Visual C++ 3.0 is incomplete and in some places
  13. incorrect. wcecompat plugs the holes and tries to bring the Windows CE
  14. CRT to a level that is more compatible with ANSI C. wcecompat goes further
  15. and provides low-level IO and stream IO support for stdin/stdout/stderr
  16. (which Windows CE does not provide). This IO functionality is not needed
  17. by the OpenSSL library itself but is used for the tests and openssl.exe.
  18. More information is available at www.essemer.com.au.
  19. Building
  20. --------
  21. Setup the eMbedded Visual C++ environment. There are batch files for doing
  22. this installed with eVC++. For an ARM processor, for example, execute:
  23. > "C:\Program Files\Microsoft eMbedded Tools\EVC\WCE300\BIN\WCEARM.BAT"
  24. Next indicate where wcecompat is located:
  25. > set WCECOMPAT=C:\wcecompat
  26. Next you should run Configure:
  27. > perl Configure VC-CE
  28. Next you need to build the Makefiles:
  29. > ms\do_ms
  30. If you get errors about things not having numbers assigned then check the
  31. troubleshooting section in INSTALL.W32: you probably won't be able to compile
  32. it as it stands.
  33. Then from the VC++ environment at a prompt do:
  34. - to build static libraries:
  35. > nmake -f ms\ce.mak
  36. - or to build DLLs:
  37. > nmake -f ms\cedll.mak
  38. If all is well it should compile and you will have some static libraries and
  39. executables in out32, or some DLLs and executables in out32dll. If you want
  40. to try the tests then make sure the ceutils are in the path and do:
  41. > cd out32
  42. > ..\ms\testce
  43. This will copy each of the test programs to the Windows CE device and execute
  44. them, displaying the output of the tests on this computer. The output should
  45. look similar to the output produced by running the tests for a regular Windows
  46. build.