B.7. CUSTOM group

The CUSTOM group, shown in Figure B.7, contains a series of settings that describe custom project options. These settings define how to build:

Figure B.7. CUSTOM group

CUSTOM group

You can also use a CUSTOM group to specify tools that are run by other CUSTOM groups, or for use in prelinker and postlinker operations.

Each CUSTOM group you create can build one or more files. The files listed under the Files value are the explicit output. So if a source and header are produced, only one is listed, and it must be the one that something else is dependent on.

If multiple files are listed using the Files value, the custom command specified is run for each file listed.

Each time the project is built, the date and time of the data file are compared against the output file and if the data is newer, the output file is rebuilt.

The default group CUSTOM=default contains an empty Custom group. If you want to build your own files, create a new group by right-clicking and selecting Make New... from the context menu. You can also select Make Copy... and then modify existing settings from the default group.

You can set up several CUSTOM groups to build different types of files. The order in which files are processed is defined by the order of the groups and dependencies.

Table B.34 describes the settings available in the CUSTOM group.

Table B.34. CUSTOM group

NameDescription
Disable

Removes or includes a CUSTOM group from a build.

Set this to False to add the group into the build. This is the default.

Setting this to True does not delete the group, but it is invisible to the build.

Description

Describes the tool to use in the custom build.

Message

Contains the message that is displayed when the custom command is run.

Files

Specifies the main output file from the custom command.

If the command produces more than one file then this entry must list only one of them. Use multiple Files entries only if you want the command run once for each of the files.

Use a fake filename, that is one that is not produced, if you want the command to run every time.

Depends_on

Specifies the files used as input data to the build process for the given custom command. When the request to rebuild is made, the data and time of this file is checked to see if it requires rebuilding. If any other dependent file in the list is newer, it is also rebuilt.

Command

Specifies the host command to run to produce the required output file or to perform the required operation.

The command can include macros, for example $@ for the output file or $? to list dependent files that are newer.

You can use any valid commands, depending on your makefile. Commands that use shell commands, for example echo and for, must be preceded by a plus sign. Using an at sign before the command prevents echoing the command before it is run.

Use_as

Specifies when and how the output files must be rebuilt.

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