Use the vacbld command to build from the VisualAge C++ command line window. Entering this command is equivalent to building from the IDE, except that the IDE itself is not available during the build and error messages appear on the console rather than in the Messages pane of the IDE
Use the vacide command to invoke the VisualAge C++ IDE from the command line.
This diagram shows the syntax of the vacbld command:

The parameters of the vacbld command are described below. All options, except the configuration file name, begin with a dash (-), and can appear in any order. You can shorten some options, provided you enter enough letters to remove ambiguity. The characters you can omit are enclosed between square brackets, [ and ].
You must specify at least one option from the following list during invocation:
If the codestore already exists, vacbld performs an incremental build that updates targets and synchronizes the codestore with any changes made to the source files and the configuration file since the last build. If the codestore does not exist, vacbld creates it.
You can specify only one of the following options:
If a codestore file is specified on the command line using the -c option, the clean option will apply to it; otherwise, the configuration file name will indicate which codestore will be cleaned up. Note that no build is performed with this option.
A
regular build from C++ source files is orderless, and
processes all source files at once. Therefore, this
option gives you an opportunity to convert your source
files for use with VisualAge C++, on a file-by-file basis.
Specifying this option is the equivalent of selecting Migration build from the Tools menu of the IDE. If you omit this option, the build is equivalent to one started by selecting Build from the Project Workbook menu of the IDE, or performing a regular build.
No persistent codestore file is produced when you build with this option. However VisualAge C++ uses a transient codestore during the build. To get a persistent codestore file, you must build again.
After
you complete a successful migration build, you can use
the configuration
optimizer to convert included header files into
primary source files.
By default, incremental builds
output only warning messages that are new since the last
build. All warning messages are stored in the codestore
and are removed when the issues to which they relate are
resolved. This option is useful if you want to clean up
all warning messages that were generated from the first
to the most recent build of your application.
You can also specify the following options:
Item 3 of 139 (2%) ... end of macro sources marker Item 169 of 305 (56%) ... body of the function double regular_emp::pay()
If incompatible options are specified, the first one specified takes precedence. The following options are incompatible:
| Option Specified | Incompatible Options |
|---|---|
| help | all other options |
| c | migrationbuild, noc |
| clean | migrationbuild, noc, showwarnings, severitylevel, showprogress |
| migrationbuild | c, clean, showwarnings, severitylevel, showprogress |
| noc | c, clean, showwarnings |
| showwarnings | clean, migrationbuild, noc |
| severitylevel | clean, migrationbuild |
| showprogress | clean, migrationbuild |
Error messages produced by vacbld are identified by an eight-character identifier that starts with "CPPC5", followed by three decimal digits. These messages appear on the console unless you redirect the standard error stream, stderr, to a file when you issue the vacbld command.
![]()
Configuration Files
Incremental C++ Builds
C Compilation: Comparing C and
C++ Builds
Codestore
![]()
Build from the Command Line
Build
Migrate Source
Files
Redirect Standard
Streams
Convert Included Source Files to
Primary Source Files
![]()
Build Options
Build Options for Compatibility with Old
C++ Compilers
