转载
http://geekswithblogs.net/BruceEitman/archive/2008/05/14/platform-builder--build-tools-intro.aspx
Platform Builder for Windows CE has become a very useful tool for developing a Windows CE platform. It does a lot of things well, but for building it can be slow. The reason is that as an IDE it has an obligation to idiot proof the build process. In doing so, it sometimes does more work than is actually necessary to take your changes and output an OS that you can run. I don't know that I would want it any other way because it makes it easier for new Windows CE developers to get started.
If you want to, you can use your expertise to speed the process along. This isn't always a good idea unless you understand what you are doing though. The reason is that you need to understand which changes require which build steps. If you do understand the reasons to do which steps you can save some time. Get it wrong and you will loose time, so over the next several posts I will explore the tools and explain what you need to know to use them.
Let's get started by listing the command line build tools. These are the tools that the IDE uses to build and knowing what they do will be to your advantage. The tools most commonly used are:
BldDemo
CEBuild
Build
NMake
BuildRel
Makeimg
Romimage
FMerge
I could probably extend that list, and may do it later. But these are the most common, and some of them I don't actually use very often, and some I don't really use directly but understanding them helps in getting things done and in solving problems when the build goes wrong.
I know that there are new Platform Builder users who spend 20 minutes, or maybe more, to build a change into an OS when the same results can be done in a minute or two. For example, a change to platform.bib or project.reg do not require a full Sysgen. If the file is copied to the release folder, you just need to run makeimg to get the change incorporated into the OS image. First we need to understand what the tools do though, and we will get to that over the next few days.
More Information，you can refer the following net address:
wince 6.0构建一般步骤：
1.sysgen :（system generation）主要是根据用户设置需求等选择wince库的组件，比如IE，mediaplay等，系统组件选择好后，可以用set命令查看环境变量和组件的配置情况。
2.build ： 整个系统构建完毕，就可以编译项目内部的源代码，这个主要包括BSP和CSP.源代码通过build.exe进行编译，build.exe将会用source和dirs的文件及makefile编译源代码。
3.release copy：将编译好的dll，exe,bib,reg,config等文件copy到release 目录下（即你建立的workspace相应的目录下）。
4.make image:合并bib,reg，dat,db等文件， 调用RomImage.exe将release目录下的文件根据ce.bib打包成nk.bin最后就可以用usb 或网络download到你的目标板了哦！
本文来自CSDN博客，转载请标明出处：http://blog.csdn.net/yjy889/archive/2009/05/07/4158810.aspx