blob: f3f77f1c32c4aba02e37d53c92f07461f73e5c95 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
/**
@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.
*/
|
