Improve Build Times

The differences between the previous versions of VisualAge C++ and this version will initially affect the build times of existing and new applications. These differences include such things as:

While you are adjusting to this new technology, you may experience slow build times. This is most noticeable with newly created configuration files. The configuration files specify C++ source files which, if written in the traditional way, specify files as #include statements. If the files specified in the #include statements are also directly specified as macro source files in the configuration files, build times will improve. By using the configuration optimizer you can automatically promote many of the header files and #include files to configuration files as macro source files. When you next perform a build, the amount of preprocessing and reprocessing of identical declarations is minimized. After the files are specified as macro source files in the configuration files you may remove the #include statements from the source files, but this action is not mandatory. (For a description of primary source files, included source files, and macro source files, click on the link for C++ Source Files and Source Regions under Related Concepts at the bottom of this file.)

Note that when you run the configuration optimizer, a build is taking place. This configuration-optimizer build may take some time, however subsequent normal builds with the newly optimized configuration file are always faster.

Faster build times may still be possible by further optimizing the configuration file. During the initial optimization not all header files may have been promoted to the configuration file as source files. Look for header files included in multiple C++ source files that are semantically the same and are not present in the configuration file. Edit the configuration file and convert these header files to primary and macro source files. Use macro source files for files that contain macro definitions that must be visible in other source files. You may want to adjust the order of these macro source files in the configuration file depending on the macro dependencies between them. For example, if header file A depends on macros defined in header file B, header file B should be specified as a macro source file and it should precede header file A in the configuration file.

The configuration optimizer may generate messages at completion that indicate what is not being promoted to the new configuration file. These messages may give you hints about further changes you can consider. For example, IBM Open Class header files that you create and directly include in your C++ source files are not promoted to the configuration file. You can add these to the configuration file.

As you develop and change your application code, you should run the configuration optimizer periodically to ensure that any new files are properly promoted to the configuration file. Every time you run a build using the IDE, a heuristic runs in the background and keeps track of the changes you make to your application. It will issue a reminder periodically to run the configuration optimizer.

You will also find that as your application grows in size, the overhead associated with the internal representation of your application (referred to as the codestore) becomes smaller. As this occurs your build-time performance will improve.

The following references link you to specific topics that can help you take advantage of the technology of this product. These files also contain links to related information. You may also find it useful to review the online tutorial. The tutorial is divided into sections that describe the features of the product (What's Cool!), that describe the new IDE (Tour of VisualAge), and that give you an opportunity to use the product while developing applications (Try VisualAge C++).



C++ Source Files and Source Regions
Codestore
Configuration Files
The Configuration Optimizer (C++)
How Configuration Files Are Processed
Incremental C++ Builds
Macros in C++ Source Files
When to Use Makefiles


Convert Included Source Files to Primary Source Files
Optimize Configuration Files after Migration


Configuration File Syntax
macros global Miscellaneous Build Option (C++)