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.
Using Visual C++ with HCL VersionVault
Learn how to use Visual C++ with VersionVault.
Browser files
Learn how to use the bscmake browser generator.

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.
      - omake
        omake can read Visual C++ makefiles, but only if NMAKE emulation mode is specified with the -EN parameter.
      - clearmake
        Learn when to use clearmake instead of omake.
      - Incremental repositories in Visual C++
        Program database files (PDBs) and incremental database files (IDBs) are built up with information from compilations of many .c or .cpp source files. This type of database file is referred to as an incremental repository.
      - Using vcmake.mak to prevent reuse mismatches
        Use vcmake.mak to prevent reuse mismatches.
      - Browser files
        Learn how to use the bscmake browser generator.
      - Using the winkin command
        If you choose a method that disables automatic winkin, you might still gain the space and performance benefits of DOs and CRs by winking in DOs manually.
  - 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.

Browser files

Learn how to use the bscmake browser generator.

The browser generator, bscmake, has a performance enhancement that can cause problems with configuration records. By default, bscmake truncates all existing browser information files (called SBRs). If you use C7 debug information to allow winkin to work automatically, running bscmake in the default mode causes winkin to fail. clearmake or omake never finds a DO that can be winked in: the SBR created when the object file was created is no longer available because bscmake overwrote it. A bscmake option is available to cause it to run in non-incremental mode, where it reads all existing SBR files without modifying them. Using this parameter with C7 debug mode permits winkin to work correctly.

To run bscmake in non-incremental mode, you must specify the /n parameter. Add this parameter on all release builds in which the DOs are versioned. To add /n using the IDE:

Click Project > Settings.
Select the desired target in the Settings For tree.
Click the Browse Info tab.
In the Project Options box, add /n.