Migrate Source Files

The migration build process allows you to migrate existing source files developed in the following environments:

A migration build fully compiles one source file at a time, compared to normal builds which perform incremental compilation only on changed files. The migration build allows you to fix any errors in the file before it proceeds to the next file. The migration build process does not make any changes to your source files.

Before using the migration build process, create a configuration file from an existing makefile using the makefile-to-configuration-file conversion aid, make2cfg. This ensures that the configuration file matches the requirements for the migration build process, and that the file has not been optimized.

To migrate your source files:

  1. Invoke the migration build process in one of the following ways:
     
  2. If the configuration file contains macro source files, the migration build process is likely to fail. If you are running the migration build process through the IDE, the migration build issues a warning and gives you the option of continuing the build or of stopping it. If you are running the migration build process with the vacbld command at the VisualAge C++ command prompt, the warning message appears and you can stop the process with the Ctrl+C key combination.

    If you stop the build, you can take one of the following actions:

  3. Correct any errors identified in the single file, and run the migration build again.
  4. Continue to run the migration build until you correct the errors in each of the files and the migration build completes successfully. Even though the tool directive (tool 'config_opt') to invoke the configuration optimizer during a normal build may have been added to the configuration file, the tool directive is ignored during the migration build.

After a Successful Migration Build

Notes:

Limitations

The migration build process should not be used with either a persistent codestore or a configuration file that has been optimized in any way.

If a persistent codestore (an .ics file), exists from an earlier build of the configuration file, it will be ignored by the migration build process. If you specify a codestore on the command line when you invoke the migration build through vacbld, it will also be ignored.

Use the make2cfg makefile conversion aid to convert your makefile to a configuration file to avoid any optimization of the configuration file.



Codestore
Configuration Files
Migration Tools


Build in the IDE
Convert Makefiles to Configuration Files
Optimize Configuration Files after Migration


Migration Build Considerations