Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Windows
Setting up a parallel build
Learn the process to set up and run parallel builds.
Overview of parallel building
HCL VersionVault can perform builds in which multiple processes execute in parallel the build scripts associated with the makefile targets.
Parallel build scheduler
Learn about parallel build scheduler.

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
- Guide to building software on Windows
  - 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 about 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.
  - 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
    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.
  - Using HCL VersionVault build tools with Java
    The build behavior of Java tools causes various problems for clearmake and omake. Understand the problems and some possible solutions to resolve them.
  - Setting up a parallel build
    Learn the process to set up and run parallel builds.
    - Overview of parallel building
      HCL VersionVault can perform builds in which multiple processes execute in parallel the build scripts associated with the makefile targets.
      - Abe environment variables
        The environment variables mentioned in this content specify information related to the abe processes.
      - Parallel build scheduler
        Learn about parallel build scheduler.
    - Setting up the client host
      Issues in setting up the client host.
    - Starting a parallel build
      Follow the steps mentioned in this content to start a parallel build.
    - Preventing parallel builds of targets
      Follow the process mentioned in this content to prevent parallel builds of targets.
    - Preventing exponential invocations of abe
      Follow the process mentioned in this content to prevent exponential invocations of abe.

Parallel build scheduler

Learn about parallel build scheduler.

clearmake schedules and manages target rebuilds as follows:

It executes the build script for an out-of-date target as soon after detection as system build resources allow.
It does not assume that executing a build script for a specific target implies that the target was updated.

clearmake evaluates the dependency graph, beginning with the targets specified on the command line. Before evaluating a specific target, clearmake ensures that all dependents of that target have been evaluated and brought up to date. As soon as a target is deemed to be out of date, it is made available for rebuilding. A rebuild is initiated as soon as system resources allow. Depending on the availability of build hosts and load-balancing settings, this might happen immediately or be delayed.

When DO shopping/winkin occurs, clearmake postpones DO lookup for any target that has scheduled dependents until the target is encountered in the rebuild logic. When such a target is detected, clearmake then attempts the DO shopping/winkin only when the dependencies of the targets are completed. This delay eliminates unnecessary rebuilds in serial mode and allows a parallel clearmake to initiate rebuilds sooner.