Using HCL VersionVault to build C++ programs

Understand the guidelines and instructions to use the VersionVault build utilities, omake and clearmake, in C++ development environments such as Microsoft Visual C++. You will learn how the makefile fragment works and also present alternate possibilities for working around the problems.

The way that C++ development environments manage their files can cause conflicts with the VersionVault build utilities. Possible symptoms of the conflict are:

• clearmake or omake rebuilds an object it could have winked in.
• When clearmake or omake winks in an incremental repository (database) file, information can be lost if the winked-in repository was not built with the same components that exist in the development view.

The exact nature of the symptoms depends on the compiler you use. For most Windows C++ compilers, these problems do not arise. The Microsoft Visual C++ environment causes a number of conflicts, which HCL VersionVault works around by including a special makefile fragment if you use the SCC integration with Visual C++.