Chapter 7 Using ClearCase to Build C++ Programs

This chapter provides guidelines and instructions for using the ClearCase build utilities, omake and clearmake, in C++ development environments such as Microsoft Visual C++. The way that C++ development environments manage their files can cause conflicts with the ClearCase build utilities. Possible symptoms of the conflict:

• 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 NT C++ compilers, these problems do not arise. The Microsoft Visual C++ environment causes a number of conflicts, which Rational ClearCase works around by including a special makefile fragment if you use the SCC integration with Visual C++. This chapter describes how this makefile fragment works and also presents alternate possibilities for working around the problems.

These C++ compilers apparently do not cause any conflict with ClearCase building:

• Borland C++

• Symantec C++

• Watcom C/C++