During a build, you can run command line programs. Do this to perform activities during a build that are not integrated into the VisualAge C++ kernel. For example, you can create directories and move files, perform some network activities, or run your own programs that have some other role in your build procedure.
You can start programs from the configuration files in one of the following ways:
Take advantage of build extensions
VisualAge C++ builds recognize certain command line tools and
utilities as build extensions. The
documentation for each command line program supplied with
VisualAge C++ tells you if it is available as a build extension and, if
it is an extension, how to run it from your configuration file.
Some build extensions run automatically when you specify a source file that is of the type that the build extension processes. For example, the resource compiler is run implicitly if you specify a resource source file as a source for a build. To run other build extensions, such as the configuration optimizer, you must use the tool directive in your configuration file.
Not all build extensions have command line equivalents. For example, the only way to run the C compiler is as a build extension.
Use the run directive to start any
command line program
You can supply any sequence of command line strings to the run directive, and specify whether
the commands are to be run before or after the compile and link
steps of the build. The commands run synchronously as a child
process of the build.
Process a makefile
The make utility is itself a build extension. If you supply a file of
type .mak as a source to a VisualAge C++ build, the make utility
processes that makefile.
Typically, you do this to set up the environment at the start of
the build process or to run tools that are not integrated into
the IDE. You can use makefiles much like you do in
traditional programming environments, including earlier versions
of VisualAge C++ and predecessor products, except that you cannot compile or link
directly from a makefile.
![]()
Configuration Files
How Configuration Files Are
Processed
Build Extensions and Extension
Specification Files
When to Use Makefiles
![]()
Change a Build Setup
Build
Run the Make
Utility
Use Makefiles as Sources for a Build
