Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Windows
Pointers on using HCL VersionVault build tools
Learn about how to use VersionVault build tools.
Accommodating build avoidance
Learn about clearmake build avoidance.
Using a recursive invocation of omake or clearmake
Understand the advantage of using a recursive invocation of omake or clearmake.

Using a recursive invocation of omake or clearmake

Understand the advantage of using a recursive invocation of omake or clearmake.

You can eliminate the problem of different build scripts described in Handling targets built in multiple ways by adding a recursive invocation of clearmake to the makefile in app_src:

..\util_src\test_prog_3.exe: ...
cd ..\util_src & $(MAKE) test_prog_3.exe

Note: In this script example, ($(MAKE) invokes omake or clearmake recursively.

Now, the target test_prog_3 is built the same way in both directories. You can turn on build-script comparison again, by removing the .NOCMP_SCRIPT or .NO_CMP_SCRIPT special target.