Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Linux and UNIX
clearmake makefiles and BOS files
The HCL VersionVault build program, clearmake can process makefiles.
Conflict resolution
Learn how to resolve conflicts that can occur in specifications of make macros and environment variables.

Managing change and releases
Learn how to manage change and release in the product.
- Managing software projects
- Workflow for creating projects
- Workflow for making baselines
- Workflow for recommending baselines
- Guide to building software on Linux and UNIX
  - HCL VersionVault build concepts
    HCL VersionVault supports makefile based building of software systems and provides a software build environment closely resembling that of the make program.
  - Derived objects and configuration records
    Learn about derived objects and configuration records.
  - Pointers on using HCL VersionVault build tools
    Learn how to use VersionVault build tools.
  - Working with DOs and configuration records
    You can perform operations on derived objects and configuration records.
  - clearmake makefiles and BOS files
    The HCL VersionVault build program, clearmake can process makefiles.
    - Makefile overview
      A makefile contains a sequence of entries, each of which specifies a build target, some dependencies, and the build scripts of commands to be executed.
    - Build options specification files
      A build options specification (BOS) file is a text file containing macro definitions and/or HCL VersionVault special targets.
    - Format of makefiles
      Understand the special considerations for using makefiles with clearmake.
    - Sharing makefiles between UNIX or Linux and Windows
      You can share makefiles between UNIX, Linux, and Windows.
    - BOS file entries
      You can put some entries in BOS files.
    - Conflict resolution
      Learn how to resolve conflicts that can occur in specifications of make macros and environment variables.
    - SHELL environment variable
      Learn about the SHELL environment variable.
    - CCASE_BRANCH0_REUSE environment variable
      Understand the use of the CCASE_BRANCH0_REUSE environment variable.
  - Using clearmake compatibility modes
    clearmake is designed for compatibility with existing make programs, which minimizes the changes you need to make to your makefiles.
  - Using HCL VersionVault to build C++ programs
    Use clearmake effectively with C++ programs built with various compilers.
  - Using HCL VersionVault build tools with Java
    The build behavior of Java tools causes various problems for clearmake. Understand the problems and some possible solutions to resolve them.
  - Setting up a parallel build
    Learn the process to set up and run builds that use several hosts in the local area network.
  - Building software for multiple platforms
    Learn how to address the challenge of using a single source tree to develop an application for a variety of hardware and software platforms.
  - Setting up a build on a non-VersionVault host
    There is a technique to create configuration records for a build that involves HCL VersionVault data, but is performed on a non-VersionVault host.
- Guide to building software on Windows

Conflict resolution

Learn how to resolve conflicts that can occur in specifications of make macros and environment variables.

Conflicts can occur in specifications of make macros and environment variables. For example, the same make macro might be specified both in a makefile and on the command line; or the same name might be specified both as a make macro and as an environment variable.

clearmake resolves such conflicts similarly to other make variants; it uses the following priority order, from highest to lowest:

Target-specific macros specified in a BOS file.
Target-specific macros specified in a makefile.
Make macros specified on the command line.
Make macros specified in a BOS file.
Make macros specified in a makefile.
Environment variables
Built-in macros

Using the -e option gives environment variables higher priority than make macros specified in a makefile.

Conflict resolution details: The following discussion treats this topic more precisely but less concisely.

clearmake starts by converting all EVs in its environment to make macros. (SHELL is an exception.) These EVs are also placed in the environment of the shell process in which a build script executes. Then, it adds in the make macros declared in the makefile. If this produces name conflicts, they are resolved as follows:

If clearmake was not invoked with the -e option, the macro value overwrites the EV value in the environment.
If clearmake was invoked with the -e option, the EV value becomes the value of the make macro.

Finally, clearmake adds make macros specified on the command line or in a BOS file; these settings are also added to the environment. These assignments always override any others that conflict. (A command-line assignment overrides a BOS setting of the same macro.)