12.1.2. User-defined projects

A user-defined project is set up and managed by you. If you have existing source files, RealView Debugger enables you to select the source files during project creation, or add them later.

The project information and settings are stored in a project settings file. This has the same name as the project and an extension of .prj. The file is placed in the project directory that you specify when you create a project. For example, std_proj_1.prj is the project settings file for the project named std_proj_1.

A user-defined project defines:

Note

If you have created a user-defined project, it is recommended that you open this first to load and debug the associated image, or images. This avoids the creation of an auto-project and enables you to save any new settings or changes to the build model.

Types of user-defined project

The types of user-defined project you can create and manage in RealView Debugger are:

Standard

A Standard project is composed of sources to compile, and/or assemble, and link. A Standard project might also contain a custom build model. RealView Debugger creates the project makefile automatically.

Library

A Library project enables you to compile and/or assemble files to put into a library. RealView Debugger creates the project makefile automatically.

Custom

A Custom project enables you to specify your own makefile, or to specify an external build program or script, or to use no build model.

Container

A Container project contains other projects and can be used to:

  • share components within, and between, development teams

  • divide up complex builds into libraries.

Note

By default, if you open a Container project, you are working on multiple projects. You can perform additional operations on the individual projects in a Container project.

Copy

You can copy existing user-defined projects to try variations of your application program or to test different development environments.

Note

Regardless of the type of project you create, project files can be controlled by your version control software if required. See Chapter 15 Working with Version Control Systems for details on how to do this.

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