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