Home
Managing change and releases
Learn how to manage change and release in the product.
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.
Building on a non-HCL VersionVault host
Learn how to build product variants on a non-VersionVault host.

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.
    - Overview of the HCL VersionVault build scheme
      Learn about the build scheme of VersionVault.
    - Dependency tracking of MVFS and non-MVFS files
      You can track MVFS and non-MVFS files.
    - Derived objects and configuration records
      When it finishes executing a build script, clearmake records the results, including build audit information, in the form of derived objects and configuration records.
    - Build avoidance
      Learn how clearmake attempts to avoid rebuilding derived objects.
    - Express builds
      Learn features of express builds.
    - Build auditing with clearaudit
      Learn about build auditing with clearaudit.
    - Compatibility with other make programs
      Many make utilities are available in the multiple-architecture, multiple-vendor world of open systems. The HCL VersionVault clearmake program share features with many of them and has some unique features.
    - Parallel building
      clearmake includes support for parallel building (concurrent execution of a set of build scripts on one or most hosts).
    - Building on a non-HCL VersionVault host
      Learn how to build product variants on a non-VersionVault host.
  - 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.
  - 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

Building on a non-HCL VersionVault host

Learn how to build product variants on a non-VersionVault host.

Many organizations develop multiple variants of their products, targeted at different platforms. If VersionVault is not available for some of the platforms, you can still build all the required product variants by using either cross-development or non-VersionVault access:

Cross-development allows you to perform a build on a supported host to produce executables for the unsupported host.
Non-VersionVault access allows hosts on which VersionVault is not installed to access VersionVault data, using standard network file-sharing services (such as NFS).

Non-VersionVault access takes advantage of view transparency. Through automatic version-selection, a view makes any VOB appear to be a standard directory tree. Any such VOB image can be exported to a non-VersionVault host.

Developers on the non-VersionVault host can perform builds within these VOB image directory trees, using native make utilities or other local build tools. The object modules and executables produced by such builds are stored in the view used to export the VOB.

For more information about building on a non-VersionVault host, see Setting up a build on a non-VersionVault host.