Optimize Configuration Files after Migration

The configuration optimizer changes your configuration file to make builds more efficient. It does this by converting included sources to primary sources whenever possible. This reduces the amount of preprocessing and reprocessing of identical declarations and also reduces the amount of work to rebuild your project after one of the sources is changed.

Using the Configuration Optimizer

Since the make2cfg process adds the tool directive tool 'config_opt' to the configuration file, once you complete a migration build and run a normal build, the configuration optimizer automatically creates an optimized configuration file for you. The tool directive does not appear in the new configuration file produced by the configuration optimizer.

In addition to this initial configuration file optimization, the IDE keeps track of the number of changes you make to your project and will prompt you to run the configuration optimizer.

To run the configuration optimizer in the IDE, select Optimize Configuration in the Tools menu. Or you can add the tool directive tool 'config_opt' to your configuration file and run a normal build. Your configuration file is optimized during this build, and the tool directive does not appear in the new configuration file that is produced.

The configuration optimizer creates a backup of the configuration file if any changes are made to it. The first backup has the suffix BK0, the second, BK1, and so on. After the BK9 backup is created, the sequence starts at BK0 again, and any previous backup files are overwritten.

Error Messages

The configuration optimizer will generate warning messages indicating which headers could not be promoted to sources and why.



Migration Tools


Convert Included Sources to Primary Sources (C++)
Convert Makefiles to Configuration Files
Improve Build Times
Migrate Source Files