How to build a wince6.0 Development Environment Based on Windows 7 flagship Edition

First of all, I would like to thank jeffreyli for providing a simpler method for installing wince6.0 R3. I have verified it today and it is much more convenient than the "wince6.0 R3 Installation Steps" I have prepared. Thank you very much!

For your reference, the installation steps are as follows:

* Please install the following software In Order

Visual Studio2005

Visual Studio2005Service Pack1

Visual Studio2005Service Pack1UpdateForWindows Vista/7(IfApplicable)

Windows Embedded CE6.0Platform Builder

Windows Embedded CE6.0SP1

Windows Embedded CE6.0R2

Windows Embedded CE 6.0 R3

Windows Embedded CE 6.0 R3 Update Rollup 11 / 3 / 2009

Windows Embedded CE 6.0 Cumulative product Update Rollup 12 / 31 / 2009

Windows Embedded CE 6.0   2010 QFE M01 to m07

Follow this step in WINXP to avoid any problems. However, the installation in Windows 7 flagship version still encountered some problems.

The first problem is the compatibility between vs2005 and Windows 7, as shown in.

Click the "online check solution" button and wait a moment. The prompt shown in is displayed.

As you can see, you only need to install SP1 of vs2005 and SP1 update for win7 to solve the problem of compatibility between vs2005 and Windows 7.

The incompatibility prompt shown in figure is also displayed when pb6.0 is installed.

The "online check solution" does not seem to be useful either. Click "run ".Program"Button.

Install programs as administrator. Otherwise, some exceptions may occur, as shown in.

Pay special attention to this when installing the pb6.0 patch, because the shortcut menu does not contain "Run as administrator. Here you have to think of a small way to indirectly implement the patch package program "Run as administrator". The method is as follows:

Click Start
Enter "cmd" in the search box"
At the same time, press Ctrl and shift, and then press ENTER
In this way, the command line window is run under the Administrator permission, and then the patch package of pb6.0 can be installed normally.

For the sake of insurance, I installed all the patch packages in this way, as shown in.

After the installation is complete, use the ceupdatecheck tool to check the status of the patch package, as shown in.

You can see that the patch package is completely installed normally. At this point, I am relieved that there should be no major problems. I quickly tried to compile a system based on the BSP of the simulator. The result is still small. As shown in.

The prompt in build. log is as follows:

Makefile. Def: including c: \ wince600 \ Public \ Common \ oak \ MISC \ sources. releasetype_oak
Nmake: Fatal error u1073: Don ' T know how to make ' C: \ wince600 \ osdesigns \ emulator \ wince600 \ deviceemulator_armv4i \ cesysgen \ oak \ Lib \ armv4i \ retail \ atls. Lib '
Stop.
Nmake: Fatal error u1077: ' C: \ wince600 \ SDK \ bin \ i386 \ nmake.exe ' : Return Code ' 0x2 '
Stop.

It seems to have something to do with ATL, but there is this file in the corresponding directory. Later, I suspect it has something to do with the component. I checked the "Active Template Library (ATL)" component and re-compiled it, sure enough.

The above describes the process and precautions for building a wince6.0 Development Environment Based on Windows 7 flagship edition. I want to record it in detail and make it easy for new users to make some reference.