From 20ab55f4941755ced3ff6c99abc63a68914a3cb1 Mon Sep 17 00:00:00 2001 From: Rich Salz Date: Mon, 23 May 2016 08:55:57 -0400 Subject: [PATCH] Remove INSTALL.WCE and refs to it. Reviewed-by: Richard Levitte --- INSTALL | 5 ++- INSTALL.WCE | 93 ----------------------------------------------------- NOTES.WIN | 2 -- README | 1 - 4 files changed, 2 insertions(+), 99 deletions(-) delete mode 100644 INSTALL.WCE diff --git a/INSTALL b/INSTALL index 4283e9d199..bdf67a6d7b 100644 --- a/INSTALL +++ b/INSTALL @@ -4,8 +4,7 @@ [This document describes installation on the main supported operating systems, currently the Linux/Unix family, OpenVMS and Windows. - Installation on DOS (with djgpp), MacOS (before MacOS X) - is described in INSTALL.DJGPP or INSTALL.MacOS, respectively.] + Installation on DOS (with djgpp) is described in INSTALL.DJGPP.] To install OpenSSL, you will need: @@ -21,7 +20,7 @@ please read one of these: * NOTES.VMS (OpenVMS) - * NOTES.WIN (any Windows except for Windows CE) + * NOTES.WIN (any supported Windows) Quick Start ----------- diff --git a/INSTALL.WCE b/INSTALL.WCE deleted file mode 100644 index fe1431acb7..0000000000 --- a/INSTALL.WCE +++ /dev/null @@ -1,93 +0,0 @@ - - INSTALLATION FOR THE WINDOWS CE PLATFORM - ---------------------------------------- - - Building OpenSSL for Windows CE requires the following external tools: - - * Microsoft eMbedded Visual C++ 3.0 or later - * Appropriate SDK might be required - * Perl for Win32 [commonly recommended ActiveState Perl is available - from http://www.activestate.com/Products/ActivePerl/] - You also need the perl module Text::Template. - Please read README.PERL for more information. - - * wcecompat compatibility library available at - http://www.essemer.com.au/windowsce/ - * Optionally ceutils for running automated tests (same location) - - _or_ - - * PocketConsole driver and PortSDK available at - http://www.symbolictools.de/public/pocketconsole/ - * CMD command interpreter (same location) - - As Windows CE support in OpenSSL relies on 3rd party compatibility - library, it's appropriate to check corresponding URL for updates. For - example if you choose wcecompat, note that as for the moment of this - writing version 1.2 is available and actually required for WCE 4.2 - and newer platforms. All wcecompat issues should be directed to - www.essemer.com.au. - - Why compatibility library at all? The C Runtime Library implementation - for Windows CE that is included with Microsoft eMbedded Visual C++ is - incomplete and in some places incorrect. Compatibility library plugs - the holes and tries to bring the Windows CE CRT to [more] usable level. - Most gaping hole in CRT is support for stdin/stdout/stderr IO, which - proposed compatibility libraries solve in two different ways: wcecompat - redirects IO to active sync link, while PortSDK - to NT-like console - driver on the handheld itself. - - Building - -------- - - Setup the eMbedded Visual C++ environment. There are batch files for doing - this installed with eVC++. For an ARM processor, for example, execute: - - > "C:\Program Files\Microsoft eMbedded Tools\EVC\WCE300\BIN\WCEARM.BAT" - - Next pick compatibility library according to your preferences. - - 1. To choose wcecompat set up WCECOMPAT environment variable pointing - at the location of wcecompat tree "root": - - > set WCECOMPAT=C:\wcecompat - > set PORTSDK_LIBPATH= - - 2. To choose PortSDK set up PORTSDK_LIBPATH to point at hardware- - specific location where your portlib.lib is installed: - - > set PORTSDK_LIBPATH=C:\PortSDK\lib\ARM - > set WCECOMPAT= - - Note that you may not set both variables. - - Next you should run Configure: - - > perl Configure VC-CE - - Next you need to build the Makefiles: - - > ms\do_ms - - Then from the VC++ environment at a prompt do: - - > nmake -f ms\cedll.mak - - [note that static builds are not supported under CE] - - If all is well it should compile and you will have some DLLs and executables - in out32dll*. - - <<< everyting below needs revision in respect to wcecompat vs. PortSDK >>> - - If you want - to try the tests then make sure the ceutils are in the path and do: - - > 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. - diff --git a/NOTES.WIN b/NOTES.WIN index f2fb0876d1..bed5037410 100644 --- a/NOTES.WIN +++ b/NOTES.WIN @@ -2,8 +2,6 @@ NOTES FOR THE WINDOWS PLATFORMS =============================== - [Notes for Windows CE can be found in INSTALL.WCE] - Requirement details for native (Visual C++) builds -------------------------------------------------- diff --git a/README b/README index edcf59e738..e32844ed1a 100644 --- a/README +++ b/README @@ -50,7 +50,6 @@ See the appropriate file: INSTALL Linux, Unix, Windows, OpenVMS INSTALL.DJGPP DOS platform with DJGPP - INSTALL.WCE Windows CE SUPPORT ------- -- 2.40.0