Build Options

Build options control the VisualAge C++ incremental C++ compiler, C compiler, and linker.

These options follow the same rules of syntax as all options in the configuration file. An option directive that specifies one option can take the following form:

option name(value_list)

The name of the option can be one of the compile or link options listed in the categories below. What is allowed in the list of values depends upon the specific option. If more than one value is allowed, values are separated by commas. Some options take yes or no values. In these cases, yes is assumed if the second value is omitted. For example, the following 2 lines are equivalent:

option link(exportAll, yes)
option link(exportAll) 

Option names are not case sensitive, but literal data elements are case sensitive. For example, the following two lines are also equivalent.

option opt(isolatedCall, "MyFunc")
option OPT(isolatedcall, "MyFunc")

Options are processed in the order that they appear in option directives. If they conflict, the last option specified prevails. Some combinations of options accumulate.

Not all options apply to all platforms on which VisualAge C++ runs. If you set an option that does not apply to your platform, it is ignored by the build process. You can specify options that are specific to other platforms so that your configuration file is portable between platforms.

Not all options apply to both C and C++ source files. If you specify an option for one or more source files, and none of those source files are of a type that uses that option, you receive a warning message.

Build options that apply to C and C++ are grouped into the following categories:

Language Options for C Language Options for C++

Miscellaneous Options
Code Generation Options
Optimization Options
Link Options

Miscellaneous Options
Code Generation Options
Optimization Options
Link Options

The C compiler also supports options in the following categories:

In may cases, you can use #pragma preprocessor directives in your source to achieve the same effect as specifying build options. In general, a pragma overrides the corresponding build option. There is one exception to the rule that pragmas override build options: to give you fine control over what messages are produced by a build, the report pragmas and report options in the miscellaneous options category can override #pragma info.

Some build options are used by build extensions. These options are described in discussions of using the individual build extensions.



Incremental C++ Builds
C Compilation
Configuration Files
How Configuration Files Are Processed
Build Extensions and Extension Specification Files


Add or Change Source Files
Add or Change Targets
Set Build Options
Build


Configuration File Syntax
Build Extensions Supplied with VisualAge C++