Compiling for Windows CE 2.0 using embedded Visual C++ 3.0 file copy hack

Applies To

• Windows CE 2.0
• Embedded Visual C++ 3.0

Overview

Microsoft did not include modular integration for the Windows CE 2.00 SDK in the release of Embedded Visual Tool 3.0 (eVT 3.0). This means that the eVC++ compiler cannot target for Windows CE 2.0. Users who wish to compile for Windows CE 2.0 must purchase Visual Studio 6.0 and the Windows CE Toolkit for Visual C++ 6.0.

This article outlines a series of steps that you can perform to compile against the Windows CE 2.0 compiler using the eVC++ 3.0 IDE.

This document was originally published by Brandon Streiff and documented by Pavel Koza from PDA Gold 11 February 2002.

Downloads

• eMbedded Visual Tools 3.0 (Original) 3.0.087
• Handheld PC 2.0 SDK

More Info

Programmers are sometime faced up to the task to create tiny program or utility for a machine with operating system Windows CE or Pocket PC. If you are experienced in the MS Visual C++ or Basic, this task can be easy - thanks to free download of Microsoft eMbedded Visual Tools. When you finish download of 300 MB file, you can start to develop... :-) Alas... Problem will appear, when the target computer is "powered by Microsoft Windows CE 2.0". It seems to be very ancient history (2 or 3 years) for MS. So Windows CE 2.0 is not supported in eVT. Unfortunately, I have spent some time on the similar problem. Here there is certain information about possibility to develop for computers with operating system Windows CE 2.0.

There is a lot of ways how to build a program. Unfortunately, most of them are commercial products. And that's why these are not suitable for building a tiny utility for your own purpose. Simple freeware tools may not be suitable for another reasons (e.g. too huge executable code, unstable run or not available necessary functions in the tool). The best way seems to take eVT from MS and to force it to generate code for WinCE 2.0. It seems to be an easy task - on the MS page is available SDK for HPC with Windows 2.0. Alas! (Another alas ...) SDK on the Web is "cut off" version and it doesn't work even with Windows CE Toolkit for Visual C++ 6.0, (It is determined for this toolkit!). I don't know why MS has placed unusable wreck of SDK for HPC on the Web. Surprisingly SDK for PalmPC is full and functional. They may have their reasons for it!? :-(

I found that a full and functional SDK for HPC is on CD "Windows CE Toolkit for Visual C++ 6.0". This version can be installed with eVT without problems. My sorrow - I found out no another source for functional HPC 2.0 SDK. The purchase of "Windows CE Toolkit" only for SDK is not right solution... Difference between both versions SDK is enclosed at the end of this text (I have got directory listing only). Searching discussion news on the Web gave me the instructions how to force eVT to compile for WinCE 2.0. It is from Brandon Streiff. I have tried it. And - it works! To spare your time here it is all with my comments.

1. Download eVT from the link above and run the installer will extract into 2 directories - DISK1 and DISK2. eVT is in the first of them and the second directory includes SDKs. There is included necessary HPC Pro SDK (determined for HPC with WinCE 2.11).
2. Download the file mplatsdk.exe (25 MB) from the second link above. This will extract into 2 directories listed at the end of this article.
3. Install eVT (if it is not installed already) for the next instructions eVT is installed in "c:\program files\microsoft embedded tools\".
4. You can start with amendment according to Brandon:
   1. install HPC Pro SDK e.g. to "d:\windows ce tools".
   2. install HPC SDK (version 2.0) to "d:\windows ce tools" as well
   3. made a copy of "d:\windows ce tools\wce211\ms hpc pro" for backup (for future restoration of HPC Pro SDK)
   4. delete "d:\windows ce tools\wce211\ms hpc pro\lib\arm" and "d:\windows ce tools\wce211\ms hpc pro\lib\sh4" directories, (there are no versions for WinCE 2.0)
   5. copy contents of "d:\windows ce tools\wce\lib\wce200\hpc\wcemips" over the contents of "d:\windows ce tools\wce211\ms hpc pro\lib\mips"
   6. copy contents of "d:\windows ce tools\wce\lib\wce200\hpc\wcesh" over the contents "d:\windows ce tools\wce211\ms hpc pro\lib\sh3"
   7. copy contents of "d:\windows ce tools\wce\lib\wce200\hpc\x86em" over the contents "d:\windows ce tools\wce211\ms hpc pro\lib\x86em"
   8. copy contents of "d:\windows ce tools\wce\include\hpc" over the contents "d:\windows ce tools\wce211\ms hpc pro\include"
   9. rename directory "c:\program files\microsoft embedded tools\evc\wce211" to "c:\program files\microsoft embedded tools\evc\wce211-backup"
   10. rename directory "c:\program files\microsoft embedded tools\evc\wce200" to "c:\program files\microsoft embedded tools\evc\wce211"
5. If you choose HPC Pro 2.11 platform in eVT, your type of processor and build a program, it compiles for WinCE HPC 2.0. Move file to your Handheld and try it. Attention! MFC libraries are not included in the "cut off" SDK, that's why you must use only API functions. Choose "WCE Application" as a new project.
6. The compiler warned that parameter "/MC" is unsupported. To suppress this select menu Project-Settings, choose C/C++ tab an remove parameter /M$(CECrtMT) in the Project Options.
7. If you need to develop for WinCE 2.11, you must restore HPC Pro SDK!
   
   

Acknowledgements

With thanks to Brandon Streiff and Pavel Koza for the original work. Re-published for archival purposes.