CrossWorks for ARM User Guide

•Project macros (page 54). Describes what project macros are and what they areused for.Related sections•Project explorer (page 128). Describes the project explorer and how to use it.•Project property reference. A complete reference to the properties used in theproject system.•Project file format (page 340). Describes the XML format CrossStudio uses forproject files.Project systemA solution is a collection of projects, and all projects are contained in solutions.Organizing your projects into a solution allows you to build all the projects in asolution with a single keystroke, load them onto the target ready for debugging withanother.Projects in a solution can can reside in the same or different directories. Projectdirectories are always relative to the directory of the solution file which enables you tomove or share project file hierarchies on different computers.The Project Explorer organizes your projects and files and provides quick access to thecommands that operate on them. A tool bar at the top of the window offers quickaccess to commonly used commands for the item selected in the Project Explorer.ProjectsThe projects you create within a solution have a project type which CrossStudio usesto determine how to build the project. The project type is selected when you use theNew Project dialog. The particular set of project types can vary depending upon thevariant of CrossWorks you are using, however the following project types are standardto most CrossWorks variants:•Executable — a program that can be loaded and executed.•Externally Built Executable — an executable that is not built by CrossWorks.•Library — a group of object files that collected into a single file (sometimes calledan archive).•Object File — the result of a single compilation.•Staging — a project that can be used to apply a user defined command (forexample cp) to each file in a project.44 Chapter 4 Project management