Wince tutorial 3 folder structure

Author: Wen Bin
Source: Wen BinProgramNet http://www.wenbinweb.com

The folder structure described here is not the folder structure of the wince system, but the folder structure integrated with the development environment platform builder. The folder structure is very complex and contains more than 30 thousand files and more than 2400 subfolders, if it is unclear, it will cause a lot of trouble in the future development process, or even the file cannot be found. For this folder structure, we can roughly divide it into two parts: one is the Pb installation folder and the other is the CE folder. Let's take a look at it separately.

First, let's look at the installation folder of Pb. This folder is usually installed in the system disk's program files/Windows CE platform Builder/4.20 folder. The folder structure is shown in:

In this folder structure, the CEC folder is very important. It is a package component file (. after Pb is installed, many standard operating system components, device driver components, board support package components, and platform management components are included, if you want to expand the component, you only need to place the corresponding CEC file in this folder, so it is the folder where the configuration file of the system component is located.

The utilities folder contains a useful tool that can generate the boot disk of the system and guide us to customize the CE operating system. This will be concentrated in the next chapter.

The wcetk folder contains another useful tool that can be used to test ce performance. I have not used this tool, so I am not very clear about more features.

Next, let's take a look at the CE folder. Its structure is shown in:

The Platform folder stores programs related to the specific platform. When you modify the kernel of a certain platform, you need to modify it in the folder where the specific platform is located, for example, if the emulator platform is the kernel part of the simulator, you must go to the emulator folder and change the source program in its kernel sub-folder.

Sdkfiles contain programs such as link.exe used by pbduring compilation. If you need to compile something manually, you can find the corresponding tool program in this folder.

The public folder is a public source program used by various platforms and the most frequently used subfolders. Its structure is as follows:

Most of them are system component source programs such as IE and shell. If we want to modify the behavior of a component, we can find it in the corresponding folder.

The most commonly used is the common folder. There are some sample programs in the samples sub-folder under the SDK folder under this folder, such as the source program of the big keyboard input method, we can change these source programs. The CSP folder in the oak folder under this folder is the CPU support component, and each subfolders in it is for specific CPU content, such as for ARM, IMG, sa11x1, etc, if you need to process the CPU-related parts, you can go to this folder to perform operations. In this folder, the drivers folder provides the source program for drivers of various typical devices, such as 1394 drivers, Nic drivers, and serial drivers, if you want to modify the driver or re-drive the driver, you can refer to the source program in this folder.

After talking about so many folder structures, how can such a complex folder structure be organized when the CE operating system is compiled? How does the compiler find the required files, who told the compiler how to compile it? The answer to these questions is the dirs file and the sources file. As the name suggests, one is responsible for connecting folders at all levels, and the other is responsible for compiling options.

The dirs file is a special text file located in the folder to be compiled. It specifies the name of the folder where the source program to be compiled is located.

The sources file is a special text file located in the source program folder. It contains some macro definitions. The compiler uses these macro definitions as options to determine how to compile and link these source programs.

You can use NotePad to open such a file. For more information about the meaning of each macro, see the Pb help document.

Now, this chapter is here. With these foundations, more exciting content will begin soon.