Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Linux and UNIX
Derived objects and configuration records
Learn about derived objects and configuration records.
Derived objects overview
Derived objects are created during builds with HCL VersionVault build tools. They are used for build avoidance and derived object sharing.

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.
    - Derived objects overview
      Derived objects are created during builds with HCL VersionVault build tools. They are used for build avoidance and derived object sharing.
      - Derived object naming
        Learn how to name a derived object (DO).
    - Configuration records
      A configuration record (CR) is the bill of materials for a derived object or set of DOs.
    - Kinds of derived objects
      There are two main types of derived objects (DOs), shareable DOs and nonshareable DOs.
    - Reuse of DO IDs
      The DO ID for a shareable derived object is guaranteed to be unique within the VOB, for all views.
    - Derived object reference counts
      A reference count of a DO is the number of times the derived object appears in HCL VersionVault dynamic views throughout the network.
  - 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.
  - 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

Derived objects overview

Derived objects are created during builds with HCL VersionVault build tools. They are used for build avoidance and derived object sharing.

In a parallel-development environment, many DOs with the same path name might exist at the same time. For example, a source file msg.c is being developed on three branches concurrently, in three different views. VersionVault builds performed in those three views produce object modules named msg.o. Each of these is a DO, and each has the same standard path name, for example, /vobs/proj/src/msg.o.

Note: Symbolic links created by a build script and files created in non-VOB directories are not DOs.

In addition, each DO can be accessed with VersionVault extended names:

Within each dynamic view, a standard UNIX or Linux path name accesses the DO referenced by that view. This is another example of the VersionVault transparency feature.

/view/drp/vobs/proj/src/msg.o

The DO in view drp.

/view/2_integ/vobs/proj/src/msg.o

The DO in view R2_integ.