Incremental C++ Builds

VisualAge C++ gives you an incremental build paradigm that can greatly increase your productivity, by reducing the time required to repeatedly compile and link C++ code. When you perform an incremental build, only portions of code that are affected by changes in your source are recompiled and relinked.

After you write or modify your source code, you initiate a build to create a target module that is consistent with the current state of the C++ source code. VisualAge C++ performs one of the following types of builds:

To make incremental builds work, VisualAge C++ maintains a program database called the codestore. The codestore contains information about source files, stored so that source regions much smaller than the original source files can be recompiled independently. A project must have at least one configuration file and exactly one codestore. A project have have more than one configuration file only when one master configuration file includes other configuration files with include directives. The configuration file defines the source files, target files, and options used during a build. VisualAge C++ also stores this information in the codestore and uses it to determine how the configuration changes from one build to the next.

In addition to greatly increasing the speed of builds, incremental builds give you features that you can use to improve your productivity:



Projects
Configuration Files
Codestore
C++ Source Files and Source Regions
Macros in C++ Source Files
One-Definition Rule


Convert Included Source Files to Primary Source Files
Add or Change Source Files
Add or Change Targets
Set Build Options
Build


Build Options