When to Use Makefiles

You never have to use a makefile when you develop an application with VisualAge C++. Nevertheless, the make utility is available to process makefiles. The main difference between using makefiles now and using makefiles in earlier versions of VisualAge C++ and predecessor products is that now you cannot issue commands to compile and link.

In VisualAge C++ configuration files perform much of the role played by makefiles in traditional C and C++ development environments. The only way to compile and link C code or perform an incremental C++ build is to process a configuration file. Makefiles cannot do this essential part of most builds. As a result, makefiles are no longer used to define dependencies on C and C++ source files or to ensure that C and C++ sources are recompiled if they have timestamps later than specified target files.

You no longer need makefiles. You may find that not only is it possible to do everything you require from configuration files, but also that using configuration files is simpler and less error-prone than maintaining makefiles. For example, the VisualAge C++ build process implicitly runs the processes required to build the targets you specify in your configuration file from sources you list in your configuration file.

There are two ways to combine processing makefiles with VisualAge C++ builds:

  1. You can issue the vacbld command inside a makefile to perform a command line build that processes a configuration file.
  2. You can specify your makefile as a source in your configuration file. The VisualAge C++ build process can run the make utility implicitly before the compile and link step.

You may want to use makefiles in the following circumstances:

If you use a configuration file for some steps in a build and a makefile for other steps, the program database for your build, the codestore, may not accurately reflect the state of your source files. This may cause problems for future builds.
For example, on OS/2 and Windows NT platforms you can run the library manager from the command line or from a makefile to update libraries. If the library was originally created by a build, the codestore is not updated to incorporate changes made to the library outside the build process.

If you have makefiles from earlier versions of VisualAge C++ and predecessor products, you should use the make2cfg utility to convert them into configuration files. To manually convert involves more steps than deleting the compile and link commands.



Configuration Files
Incremental C++ Builds
C Compilation
Codestore
Makefiles


Change a Build Setup
Build
Build from the Command Line
Produce Multiple Targets from One Build
Run Command Line Programs During Builds
Convert Makefiles to Configuration Files
Run the Make Utility
Use Makefiles as Sources for a Build


Build Extensions Supplied with VisualAge C++