Main Page | Namespace List | Class Hierarchy | Alphabetical List | Class List | Directories | File List | Namespace Members | Class Members | File Members | Related Pages

# ACE on Windows CE status

Last updated Tuesday 15-November-2005 by Steve Huston <shuston@riverace.com>

As of ACE 5.5, Riverace supports ACE on Windows CE building with Microsoft Visual Studio 2005 and targeting the Pocket PC 2003 SDK and Windows Mobile 5. 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.

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.

The ACE release process generates the needed Visual Studio 2005 solution and project files with "_WinCE" appended to the name (e.g. ACE_WinCE.vcproj) to distinguish them from both Win32-targeted VC8 projects (ACE_vc8.vcproj) and Visual Studio 2003 projects (ACE.vcproj). The files are generated with the "Pocket PC 2003 SDK (ARMV4)" and "Windows Mobile 5.0 Pocket PC SDK (ARMV4I)" platforms defined. To add additional platforms, the files must be regenerated using MPC.

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.

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.