RealView® Developer Kit Project Management User Guide 5.9.2. Running the custom build

5.9.2. Running the custom build

You can control the build using the Use_as settings value, shown in Figure 5.10. Right-click on the setting to see the available options:

link_dependent

RealView Debugger ensures that it is up-to-date when building the application. This is the default.

link_input

Creates an object file or library which is then linked to the application built by the project.

named_target

Makes the file a named target. This means that other files must be dependent on it for it to be used.

Use this option to create a header or source file, that is a .c or .asm file, that is then compiled or assembled in a COMPILE or ASSEMBLE group. The make utility knows to build the header or source file before building the application with it.

You can also layer custom projects in this way with the output of one project used as the input of another.

post_link

Specifies that the file is built only after linking.

Note

You can force a CUSTOM rule to run every time that you build the application by referring to a file that does not exist. For example, in the steps in Adding a custom build group, you could have specified that the file was called version but still written to version.txt. This causes the CUSTOM rule to be executed each time you build the application because the make utility decides that the file called version does not exist and so tries to build it.

To undo this change and restore the build model:

Select Project → Project Properties... to display the Project Properties window.
Right-click on the *CUSTOM=MY_GROUP group in the List of Entries pane, and select Delete from the context menu.
Select File → Save and Close to regenerate the makefile(s) for the project, and close the Project Properties window.
Select Tools → Build... to rebuild the application.

Copyright © 2005, 2006 ARM Limited. All rights reserved.	ARM DUI 0291C
Non-Confidential
PDF version