Configuring the makefile
By default, a derived object config record does not list the version of the makefile that was used to build it. Instead, the config record includes a copy of the build script itself. (Why? When a new version of the makefile is created with a revision to one target build script, the configuration records of all other derived objects built with that makefile are not rendered out of date.)
But if the monet program is to be rebuilt in this view using clearmake (or standard make on Linux and the UNIX system or omake on the Windows® system), a version of the makefile must be selected somehow. You can have clearmake record the makefile version in the config record by including the special clearmake macro invocation $(MAKEFILE) in the target dependency list in the following formats:
On the Windows system
monet.exe: $(MAKEFILE) monet.obj ...
link –out:monet.exe monet.obj ...On Linux and the UNIX system
monet: $(MAKEFILE) monet.o ...
cc –o monet ...Alternatives
The clearmake command always records the versions of explicit dependencies in the config record.
Alternatively, you can configure the makefile at the source level.
- Attach a version label to the makefile at build time.
- Then, to configure a view for building, use a config spec like the one in Historical view defined by a version label or View to modify an old configuration.
You can also use the special target .DEPENDENCY_IGNORED_FOR_REUSE. For more information, see DevOps Code ClearCase Guide to Building Software.