Use the Msdev utility to build a project or workspace file from the command line. The following examples demonstrate the proper syntax for building a project for a Palm-size PC that uses an MIPS processor and for an emulated Handheld PC (HP/C) that works with Microsoft® Windows® CE for the Handheld PC, version 2.0:
msdev Myproject.dsp /MAKE "Myproject - Win32 (WCE MIPS) Debug" /CEConfig="Palm-size PC 2.01" /REBUILD
msdev MyProject.dsp /MAKE "Myproject - Win32 (WCE X86em) Debug" /CEConfig="H/PC Ver. 2.00" /REBUILD
Use the Nmake utility to build makefiles. When linking files, use the correct subsystem flag for your target platform. If you are working within Visual Studio, the toolkit provides the correct flag automatically; do not change it. When using Nmake from the command line, refer to the following table to specify the correct subsystem flag.
| Target platform | Subsystem flag |
|---|---|
| Standard Win32 target | -subsystem:windows |
| Windows CE emulation | -subsystem:windows -windowsce:emulation |
| Windows CE-based remote device | -subsystem:windowsce, *
* = version number, such as 2.10 |
The following examples demonstrate the proper syntax for building makefiles for a Palm-size PC; for an H/PC that works with Microsoft Windows CE for the Handheld PC, version 2.0; or for an H/PC that runs Microsoft Windows CE, Handheld PC Professional Edition, version 3.0:
nmake -f"MYPROJ.MAK" CESubsystem=windowsce,2.0 CEVersion=200
CEConfigName="H/PC Ver. 2.00"
nmake -f"MYPROJ.MAK" CESubsystem=windowsce,2.01 CEVersion=201
CEConfigName="Palm-size PC 2.01"
nmake -f"MYPROJ.MAK" CESubsystem=windowsce,2.11 CEVersion=211
CEConfigName="H/PC Pro Ver. 2.11"
You can build target environments for any of the following processors:
Batch files for building these environments are located in the Windows CE Tools\WCE211\BIN directory. These batch files are templates only; you must modify them for your project before you can use them.