Windows Embedded ce 6.0 initial development experience (6) Customized platform favorites

In the previous article "Windows Embedded ce 6.0 initial development experience", "Building CE platform"

Http://blog.csdn.net/aawolf/archive/2007/12/19/1953448.aspx

 

Windows CE is a componentized operating system. We can set different components based on different environments to form a targeted platform. However, a function can be implemented only by multiple components. Catalog is a set of components that implement a function. Each catalog item contains one or more components, while catalog item requires a function. When this function is required for our platform, select the corresponding catalog item to the platform.

After the wizard for creating the platform is complete, we enter the Pb ide interface. The catalog items view and Solution Explorer are in the same region. You can switch between them as needed.

In the catalog items view, we can see that the catalog in CE can be divided into the following categories: BSP (board-level support package); core OS (components included in the operating system ); device Drivers (driverProgramClass); platform manager (platform manager) and third party (third-party components ). Most of the components that implement functions are included in core OS.

If you want to add a game to the platform, choose "core OS"-"cebase"-"Application-end user"-"games": freecell and solitaire.

In addition to adding catalog to the platform, we can also add our own files and registry information.

Switch the view back to Solution Explorer. We can see all the files contained in the Platform. Select "connectcore 9p" in "parameter files", which contains the project. reg file. Double-click the file to add some registry information. The registry information appears in the registry of the target device.

 

In addition, in the C:/wince600 platform-cc9p-parameter files, we can also see the platform. reg file. The platform. reg file is for all platforms running on the cc9p Development Board, while project. Reg is only for the current development platform.

If you want to add your own files to the platform, you need to use the bib file. If you want to introduce some batch processing operations, you need to use the DAT file. We usually use the project. bib and project. DAT files.

 

The standard format of bib files consists of the target file name, source file path and name, and memory type. The target file name refers to the file name on the target device. If no path is specified, the file name appears in the \ Windows directory by default. The second part is the source file path and name, which refers to the file path on the PC; the last part is the memory type, if you want to compile the file to NK. in bin, specify as NK. Separate the three parts with spaces. Bib files support macros. We can add different files to NK. bin by specifying different environment variables.

 

To specify the environment variables, right-click digios in Solution Explorer and select Properties from the menu. In the Properties dialog box, select environment, and then we can add our own environment variables.

 

The environment variable has two values: 1 or <null>. Here we create an environment variable named "img_netcf_csapp. If the variable is 1, The bibfile will contain the hello_mvp.exe file to NK. Bin.

If you want to perform other operations, you must use the DAT file. The DAT files here are the same as those on the PC platform and are also batch files. For example, we can copy a shortcut file (. lnk) from the \ Windows directory to the \ windows \ Startup directory. In this way, when the operating system is started, the executable file corresponding to the lnk file will be executed.

 

Now, the customization of our platform will come to an end. We learned how to add catalog items, files, and registry entries to the platform and perform batch processing. Next, we can compile and debug the customized platform.

Next "Compilation and debugging platform" in "Windows Embedded ce 6.0 initial development experience"
Http://blog.csdn.net/aawolf/archive/2008/02/03/2079664.aspx

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/aawolf/archive/2008/01/12/2039866.aspx

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/aawolf/archive/2008/01/12/2039866.aspx