tool Configuration File Directive

You should not use this directive unless the instructions for using a feature supplied with VisualAge C++ tell you to apply the tool directive.

The tool directive runs build extensions. Build extensions add capabilities to the VisualAge C++ build process but are not part of the VisualAge C++ kernel. Some build extensions are also available as command line programs, but you do not use the run directive to run them during a build.

Most build extensions are run automatically when a source file specified with a source directive is the type of file that the build extension takes as input. For example, you can use the resource compiler and C compiler without being aware that they are build extensions. You use the tool directive when the build process needs more information than is provided by the source directive to determine that a build extension must be run, or if the build extension does not require a source file as input.

This diagram shows the syntax of the tool directive:

The tool directive has one parameter:

string
This parameter identifies the extension.

For example, the configuration optimizer is a build extension. If you are using the IDE, you can run it without modifying your configuration file, by selecting Optimize Configuration from the Tools menu. If you are not using the IDE, run the configuration optimizer by including the following directive in your configuration file:

tool "config_opt"

When the tool directive is processed, options that are in effect and apply to the build extension are passed to the build extension.



Configuration Files
How Configuration Files Are Processed
Build Extensions and Extension Specification Files


Change a Build Setup
Build
Run Command Line Programs During Builds


Configuration File Directives
Build Options
Build Extensions Supplied with VisualAge C++