summaryrefslogtreecommitdiff
path: root/docs/CE-status.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/CE-status.txt')
-rw-r--r--docs/CE-status.txt41
1 files changed, 0 insertions, 41 deletions
diff --git a/docs/CE-status.txt b/docs/CE-status.txt
deleted file mode 100644
index f3f77f1c32c..00000000000
--- a/docs/CE-status.txt
+++ /dev/null
@@ -1,41 +0,0 @@
-/**
-@page wince ACE on Windows CE status
-
-Last updated Tuesday 04-March-2003 by Steve Huston <shuston@riverace.com>
-
-@subsection ce_status Status
-
-As of ACE 5.3, Riverace supports ACE on Windows CE 3 with the
-PocketPC 2002 SDK and on Windows CE 4 with the Standard SDK.
-OCI supports TAO 1.3 on at least Windows CE 3 with the PocketPC 2002 SDK.
-Contact the individual support provider for complete information regarding
-these platforms as well as the supported hardware targets.
-
-@subsection ce_evc eMbedded Visual C++ Projects
-
-Whereas previous ACE versions had separate ACE and ACE_OS eMbedded Visual C++
-project files, the project and workspace arrangement is now the same as
-for other Windows versions. The project and workspace files themselves are
-generated using the MakeProjectCreator tool when the ACE kit is prepared.
-Both EVC3 and EVC4 use the same project and workspace files.
-
-Developers working with sources checked out from CVS must generate the
-project and workspace files locally using MPC. The autobuild system's
-generate_makefile and generate_workspace commands can be used for this.
-
-@subsection ce_wchar Unicode/WChar
-
-ACE on WindowsCE automatically has ACE_HAS_WCHAR and ACE_USES_WCHAR turned
-on. Thus ACE_TCHAR and ACE_TEXT() are the wide char versions.
-
-@subsection ce_tests Running the Test Suite on Windows CE
-
-The ACE test suite in ACE_wrappers/tests is used on Windows CE as well as
-on dekstop Windows. The test suite tools are being extended to use a
-product called Pocket Controller, Enterprise edition from Soft Object
-Technologies, Inc. (www.soti.net) that can script the actions needed to
-copy the test files to a PocketPC device, run the test, and copy the log
-files back to the build machine for analysis and reporting to the
-scoreboard.
-
-*/ \ No newline at end of file