Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Linux and UNIX
Pointers on using HCL VersionVault build tools
Learn how to use VersionVault build tools.
Continuing to work during a build
As your build progresses, other developers continue to work on their files and might check in new versions of elements that your build uses.

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.
    - Running clearmake
      You can run clearmake from the command line or from the VersionVault File Browser (xclearcase).
    - A simple clearmake build scenario
      clearmake is designed to let developers in makefile-based build environments continue working in their accustomed manner.
    - Accommodating build avoidance
      Learn about clearmake build avoidance.
    - Declaring source dependencies in makefiles
      To implement build avoidance based on time stamps, standard make variants require you to declare all the source file dependencies of each build target.
    - Build-order dependencies
      In addition to source dependencies, makefiles also contain build-order dependencies.
    - Problems with forced builds
      Understand the problems with forced builds.
    - How clearmake interprets double-colon rules
      Double-colon rules are a special kind of makefile construct that allows several independent rules for one target, each with a possibly different build script.
    - Continuing to work during a build
      As your build progresses, other developers continue to work on their files and might check in new versions of elements that your build uses.
    - Using config spec time rules
      If you use a UCM view, your config spec is generated by HCL VersionVault. Do not add time rules to your config spec.
    - Build sessions, subsessions, and hierarchical builds
      Learn about HCL VersionVault build auditing.
    - Build auditing and background processes
      If some conditions are met, HCL VersionVault build programs audit background processes correctly.
    - Working with incremental update tools
      The design of the build auditing capability makes it ideal for use with tools that build derived objects from scratch.
    - Adding a version string or time stamp to an executable
      You can incorporate a version string and/or time stamp into a C-language compiled executable using simple techniques.
  - 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
    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

Continuing to work during a build

As your build progresses, other developers continue to work on their files and might check in new versions of elements that your build uses.

If your build takes an hour to complete, you do not want build scripts executed early in the build to use version 6 of a header file and scripts executed later to use version 7 or 8.

To prevent such inconsistencies, any version whose selection is based on a LATEST config spec rule is locked out if it is checked-in after the instant that clearmake was invoked. The moment that the clearmake build session begins is the build reference time.

The same reference time is reported in each configuration record produced during the build session, even if the session lasts hours (or days):

% cleartool catcr hello.o

Target hello.o built by drp.dvt
Host "fermi" running OSF1 V1.3 (alpha) 
Reference Time 26-Feb-03.16:53:58, this audit started 
26-Feb-03.16:54:10 ...

Note: The reference time is the build reference time, when the overall clearmake build session began. The this audit started time is when the execution of the individual build script began.

When determining whether an object was created before or after the build reference time, clearmake adjusts for clock skew, the inevitable small differences among the system clocks on different hosts. For more information about build sessions, see Build sessions, subsessions, and hierarchical builds.

CAUTION: A coordinated reference time of a build applies to elements only, providing protection from changes made after the build began. You are not protected from changes to view-private objects and non-MVFS objects. For example, if you begin a build and then change a checked-out file used in the build, a failure might result. To avoid this problem, do not work on the same project in a view in which a build is in progress.