Detailed description of the Build OS menu of Platform Builder 5.0

// ================================================ ========================================
// TITLE:
// Detailed description of the Build OS menu of Platform Builder 5.0
// AUTHOR:
// Norains
// DATE:
// Saturday 05-rjl-2008
// Environment:
// PB 5.0 + DB1200 BSP
// ================================================ ========================================

Many new users have some questions about the Build OS menu of Platform Builder 5.0 (hereinafter referred to as PB 5.0), but do not know how to choose it in actual use. Here I will give some explanations based on my usual experience.

The first group is the compilation command. There are three in total:

1. Sysgen

Generate a system image based on the current system design. This operation does not change the files that have been compiled (Build. The file mentioned here refers to the OS file, that is, various lib libraries located under the WINCE500 folder.

Note the following three points:

1). After the last Sysgen call, if you have added or removed files and related Catalog, we strongly recommend that you select "Clean Before Building" and start a new Sysgen. This will minimize the chance of errors.

2). This command will also compile the Project included in the system design Workspace ).

3). No files are copied to the target (Release) folder.


2. Build and Sysgen

In fact, this is a combination of the two commands, first compile (Build), and then call Sysgen. This command not only compiles Public code, but even Private code, so it takes a long time. This command is recommended only when you change the OS source file.

This command is the same as the previous sysgen command. It also compiles projects included in the system design workspace and does not copy files to the target (release) folder.



The following three are command labels used to partially control the behavior of commands during running.

3. Build and sysgen current BSP

Compile (build) and then sysgen the current BSP package. Like the previous two commands, the command does not copy files to the target (release) folder.

Note that, based on actual usage experience, because of different command parameters, sometimes, even if you can successfully call the sysgen generation system, it is possible to call this command to compile the BSP package. In this case, you can only handle the problem based on the actual situation.


4. clean before building

If this label is selected, the last file created by sysgen will be cleared before the command is executed.


5. Copy Files to Release Directory

If this label is selected, the generated file will be copied to the target (Release) folder after compilation. Generally, this target (Release) folder is the directory where your project is located.

This label is selected by default.


6. Make Run-Time Image After Build

If this label is selected, a run-time image is generated after compilation ). The most typical running image is NK. BIN.

After you create a new project, the tag is selected by default.

 

The last is a group of auxiliary commands.

7. Copy Files to Release Directory

Copy the generated file to the target (Release) folder.

8. Make Run-Time Image

Generate a Run-Time Image ). The most common is to combine compiled files into nk. bin.


9. Batch Build

Used to select multiple configurations to generate a Run-Time Image ).


10. Open Release Directory

Open the command line window. The default path is the target (Release) folder.


11. Set Active Configuration

Select an existing configuration as available.


12. Deployments

You can use this command to add or delete configurations.


You can refer to Platform Builder User's Guide> Platform Builder IDE> Platform Builder User Interface> Menu Descriptions for details about these commands.