For incremental C++ build to work, VisualAge C++ must maintain a database that stores information about each build. This program database is called the codestore. The codestore is a database that is created or updated during builds. A build synchronizes the codestore with the latest version of source code.
A project has one codestore and at least one configuration file. A codestore can be produced with more than one configuration file only when one master configuration file includes other configuration files with include directives. The codestore file has the same name as the configuration file, or master configuration file, and the file extension .ics. VisualAge C++ records information from the configuration file and from C++ source files in the codestore. On all but an initial build, VisualAge C++ also uses data in the codestore to determine what has changed from one build to the next.
The
codestore holds a representation of C++ code that provides rapid
access for services such as code generation, debugging, and
browsing. Several components of VisualAge C++ use the codestore. The
IDE accesses information in the codestore to let you browse code.
You do not have to perform a special build or set any build
options in your configuration file to browse or debug C++ code.
All information required by the C++ debugger is in the codestore,
and not in the target file produced by the build. Therefore, you
can produce an application that you can ship and code that you
can debug from one build. This is a great advantage over
traditional compilers.
The one-definition
rule applies to a codestore. This rule limits when you can
redefine variables, functions, class types, enumeration types,
and templates.
Every time you build in the IDE or run the vacbld command, you create or update a transient or persistent codestore. A transient codestore is a temporary codestore that resides in transient memory. It is used during one run of vacbld or one IDE session and is erased when you close the IDE or vacbld ends. A persistent codestore is a codestore that is saved in a file. It remains after you close your IDE session or vacbld ends, and is available for future builds. By default, a persistent codestore is created at the end of an IDE session during which at least one build was performed and by the vacbld command.
To increase the speed of builds, the IDE can use both transient and persistent codestores. By default, the IDE uses a transient codestore and creates or updates the persistent codestore at regular intervals.
When you build by selecting Build in Migrate Mode from the Project Workbook menu in the IDE or by running vacbld with the -migrationbuild or -noc options, a transient codestore is used during the build and no persistent codestore file created.
The build process does not modify your source files. You can delete the codestore file at any time. The best way to remove an existing codestore is to select Clean from the Project Workbook menu of the IDE, because Clean performs additional cleanup. The next time you build, VisualAge C++ performs an initial build and creates a new codestore.
![]()
Projects
Incremental C++ Builds
C Compilation: Comparing C and C++ Builds
Configuration Files
C++ Source Files and Source Regions
One-Definition Rule
Cleaning Up After Builds
![]()
Add or Change Source
Files
Add or Change Targets
Migrate Source
Files
Set Build Options
Build
