To start developing an application, first create a new project. To create a new project:
The New Project dialog appears. This dialog displays the set of project types (Categories) and project templates.
We'll create a project to develop our application in C:
Here you can customize the project by altering a number of common project properties, such as an additional file format to be output when the application is linked and what library support to include if you use printf and scanf. After the project is created, you can change these settings in the Project Explorer as needed.
The Links to system files group shows the links to CrossWorks system files that will be created in the project. Because these files are links, the default behavior is that they will be shared with other projects—so modifying one will affect all projects containing similar links. To prevent accidental modification, these files are created as read-only. Should you wish to modify a shared file without affecting other projects, first import it into the project. (Importing a shared file will be demonstrated later in this tutorial.) See Creating and managing projects for more information on project links.
The Project files pane shows the files that will be copied into the project. Because these files are copied to the project directory, they can be modified without affecting any other project.
If you uncheck an item, that file is not linked to, or created in, the project. We will leave all items checked for the moment.
Here you can specify the default configurations that will be added to the project. See Creating and managing projects for more information on project configurations.
This will create a project for a generic ARM 7 device with RAM located at address 0x00000000. This is fine, because we are going to run this example on the simulator. ARM hardware, however, is rarely so accommodating because memory will be mapped at different addresses, target-specific startup code may be required to initialize peripherals, different techniques need to be employed to reset the target, and target-specific loader applications are required to program flash memory. To create a project to run on hardware, you should instead select a template from the project type matching your target—that will create a project with the memory maps, startup code, reset script, and a flash loader for your target.
The Project Explorer shows the overall structure of your project. To invoke it, do one of the following:
This is what our project looks like in the Project Explorer:
The project name is shown in bold to indicate it is the active project (and, in our case, the only project). If you have more than one project, you can set the active project by using the drop-down box on the Build tool bar or by right-clicking the desired project's name in the Project Explorer to display the shortcut menu with the Set as Active Project command.
The files are arranged into two groups; click the + symbol next to the project name to reveal them:
Files stored outside the project's home directory (with a small purple shortcut indicator at the bottom left of the icon, as above.
These folders have nothing to do with directories on disk, they are simply a means to group related files in the Project Explorer. You can create new folders and specify filters for them based on the project files' extensions; thereafter, when you add a new file to the project, it will be shown in the Project Explorer folder whose filter matches the new file's extension.