X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=blobdiff_plain;f=INSTALL.WCE;h=ac587d6bd267ff3958774444af798b4e337e390d;hp=7de7faaa1d8980dd2484784176e126d18ab868e7;hb=e5b0508a145178dc86bfbca44139d9a3c65254ae;hpb=0bf23d9b2055223c6e7a1398d2243a65dfa4c30d

diff --git a/INSTALL.WCE b/INSTALL.WCE
index 7de7faaa1d..ac587d6bd2 100644
--- a/INSTALL.WCE
+++ b/INSTALL.WCE
@@ -8,6 +8,12 @@
   * 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.  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 +26,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 +64,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.
+