12.7.2. Project Properties window

The Project Properties window enables you to customize your project in the same way that you configure other settings files, such as build tool properties and workspace settings. This window contains many of the same controls and menus that are used to configure settings described in other parts of the RealView Debugger documentation. For general instructions on how to use these common controls and menus, see the Changing Settings topic in the RealView Debugger online help. The rest of this section describes the controls that are specific to setting up your projects.

Select Project → Project Properties... from the default Code window main menu to display the Project Properties window, shown in Figure 12.7.

Figure 12.7. Project Properties window

Project Properties window

Figure 12.7 shows the properties for a Standard project, for example dhrystone.prj. Other types of project have a different set of properties.

The left pane of the Project Properties window, the List of Entries pane, shows project settings as a hierarchical tree with node controls. The right pane, the Settings Values pane, displays the contents of any group that you select in the left pane.

The first setting in the List of Entries pane, the left pane, of the Project Properties window is the name of the project settings file, for example examples_directory\dhrystone\dhrystone.prj. When selected, the Description field shows the full pathname of this project settings file.

Other settings below the project settings file specify groups of settings. Each group defines that part of the build model covered by the contents. For example, in a Standard project the CONFIGURATION group defines the build target configurations and the COMPILE group defines the compilation stage.

Where appropriate, a project might contain multiple groups, for example an interworking project that uses both ARM and Thumb code. Use unique names to identify multiple groups for this type of project.

If a group is disabled, the entry in the left pane is grayed out, shown in Figure 12.7. You can delete disabled groups but this is not necessary. Any group that is disabled is ignored for the project, even if entries in the group are set (see Disabling a group for details). If you delete a disabled group, it might be harder to change the project later.

Where permitted, groups can be deleted, renamed or copied. Making a copy of an existing group creates a group that can then be edited in the usual way. If the group you are copying is marked by an asterisk, the copy is also marked in the same way.

You can also make a new group so that you can configure the build model to your specification and choose appropriate names for the groups in the project. Making a new group creates a new container for the default settings. See Configuring project properties for examples of how to work with groups.

Copyright © 2003, 2004 ARM Limited. All rights reserved.ARM DUI 0234B
Non-Confidential