Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Windows
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.

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 clearmake or omake instead of other make programs
      clearmake and omake ensure correct reuse decisions of different versions of files selected by a config spec, determine the complete dependency list accurately with build auditing, and allow identical derived objects from other views to be winked in to the current view.
    - Using Visual C++ with HCL VersionVault
      Learn how to use Visual C++ with VersionVault.
  - 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.

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.

The way that C++ development environments manage their files can cause conflicts with the VersionVault build utilities. Possible symptoms of the conflict are:

clearmake or omake rebuilds an object it could have winked in.
When clearmake or omake winks in an incremental repository (database) file, information can be lost if the winked-in repository was not built with the same components that exist in the development view.

The exact nature of the symptoms depends on the compiler you use. For most Windows C++ compilers, these problems do not arise. The Microsoft Visual C++ environment causes a number of conflicts, which HCL VersionVault works around by including a special makefile fragment if you use the SCC integration with Visual C++.