Back to home page

openssl Cross Reference

 
 

    


0001  
0002  INSTALLATION FOR THE WINDOWS CE PLATFORM
0003  ----------------------------------------
0004 
0005  Building OpenSSL for Windows CE requires the following external tools:
0006 
0007   * Microsoft eMbedded Visual C++ 3.0 or later
0008   * Appropriate SDK might be required
0009   * Perl for Win32 [commonly recommended ActiveState Perl is available
0010     from http://www.activestate.com/Products/ActivePerl/]
0011 
0012   * wcecompat compatibility library available at
0013     http://www.essemer.com.au/windowsce/
0014   * Optionally ceutils for running automated tests (same location)
0015 
0016   _or_
0017 
0018   * PocketConsole driver and PortSDK available at
0019     http://www.symbolictools.de/public/pocketconsole/
0020   * CMD command interpreter (same location)
0021 
0022  As Windows CE support in OpenSSL relies on 3rd party compatibility
0023  library, it's appropriate to check corresponding URL for updates. For
0024  example if you choose wcecompat, note that as for the moment of this
0025  writing version 1.2 is available and actually required for WCE 4.2
0026  and newer platforms. All wcecompat issues should be directed to
0027  www.essemer.com.au.
0028 
0029  Why compatibility library at all? The C Runtime Library implementation
0030  for Windows CE that is included with Microsoft eMbedded Visual C++ is
0031  incomplete and in some places incorrect.  Compatibility library plugs
0032  the holes and tries to bring the Windows CE CRT to [more] usable level.
0033  Most gaping hole in CRT is support for stdin/stdout/stderr IO, which
0034  proposed compatibility libraries solve in two different ways: wcecompat
0035  redirects IO to active sync link, while PortSDK - to NT-like console
0036  driver on the handheld itself.
0037 
0038  Building
0039  --------
0040 
0041  Setup the eMbedded Visual C++ environment.  There are batch files for doing
0042  this installed with eVC++.  For an ARM processor, for example, execute:
0043 
0044  > "C:\Program Files\Microsoft eMbedded Tools\EVC\WCE300\BIN\WCEARM.BAT"
0045 
0046  Next pick compatibility library according to your preferences.
0047 
0048  1. To choose wcecompat set up WCECOMPAT environment variable pointing
0049     at the location of wcecompat tree "root":
0050 
0051     > set WCECOMPAT=C:\wcecompat
0052     > set PORTSDK_LIBPATH=
0053 
0054  2. To choose PortSDK set up PORTSDK_LIBPATH to point at hardware-
0055     specific location where your portlib.lib is installed:
0056 
0057     > set PORTSDK_LIBPATH=C:\PortSDK\lib\ARM
0058     > set WCECOMPAT=
0059 
0060  Note that you may not set both variables.
0061 
0062  Next you should run Configure:
0063 
0064  > perl Configure VC-CE
0065 
0066  Next you need to build the Makefiles:
0067 
0068  > ms\do_ms
0069 
0070  If you get errors about things not having numbers assigned then check the
0071  troubleshooting section in INSTALL.W32: you probably won't be able to compile
0072  it as it stands.
0073 
0074  Then from the VC++ environment at a prompt do:
0075 
0076    > nmake -f ms\cedll.mak
0077 
0078  [note that static builds are not supported under CE]
0079 
0080  If all is well it should compile and you will have some DLLs and executables
0081  in out32dll*. 
0082 
0083  <<< everyting below needs revision in respect to wcecompat vs. PortSDK >>>
0084 
0085  If you want
0086  to try the tests then make sure the ceutils are in the path and do:
0087  
0088  > cd out32
0089  > ..\ms\testce
0090 
0091  This will copy each of the test programs to the Windows CE device and execute
0092  them, displaying the output of the tests on this computer.  The output should
0093  look similar to the output produced by running the tests for a regular Windows
0094  build.
0095