Fix typo in INSTALL.WCE.

[openssl.git] / INSTALL.WCE

diff --git a/INSTALL.WCE b/INSTALL.WCE
index 7de7faaa1d8980dd2484784176e126d18ab868e7..adc03f41d4c500c23e02e703f1473b098c552c74 100644 (file)
--- a/INSTALL.WCE
+++ b/INSTALL.WCE
@@ -8,6 +8,15 @@
   * wcecompat compatibility library (www.essemer.com.au)
   * Optionally ceutils for running automated tests (www.essemer.com.au)
 
+ You also need Perl for Win32.  You will need ActiveState Perl, available
+ from http://www.activestate.com/ActivePerl.
+
+ Windows CE support in OpenSSL relies on wcecompat and therefore it's
+ appropriate to check http://www.essemer.com.au/windowsce/ for updates in
+ case of compilation problems. As for the moment of this writing version
+ 1.1 is available and actually required for WCE 4.2 and newer platforms.
+ All Windows CE specific issues should be directed to www.essemer.com.au.
+
  The C Runtime Library implementation for Windows CE that is included with
  Microsoft eMbedded Visual C++ 3.0 is incomplete and in some places
  incorrect.  wcecompat plugs the holes and tries to bring the Windows CE
@@ -20,9 +29,6 @@
  Building
  --------
 
- You need Perl for Win32.  Unless you will build on Cygwin, you will need
- ActiveState Perl, available from http://www.activestate.com/ActivePerl.
-
  Setup the eMbedded Visual C++ environment.  There are batch files for doing
  this installed with eVC++.  For an ARM processor, for example, execute:
 
@@ -61,3 +67,8 @@
  > cd out32
  > ..\ms\testce
 
+ This will copy each of the test programs to the Windows CE device and execute
+ them, displaying the output of the tests on this computer.  The output should
+ look similar to the output produced by running the tests for a regular Windows
+ build.
+