Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Linux and UNIX
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.
Performing an audited build in the export view
You can perform an audited build in the export view.

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.
  - 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.
    - Build scenario
      Let us consider a build scenario.
    - Setting up an export view
      An HCL VersionVault export view allows limited access to one or more VOBs by using standard NFS export facilities.
    - Mounting the VOB through the export view
      Learn how to mount the VOB through the export view.
    - Revising the build script
      To produce an audited build on a non-HCL VersionVault host, you must revise the build script.
    - Performing an audited build in the export view
      You can perform an audited build in the export view.
- Guide to building software on Windows

Performing an audited build in the export view

You can perform an audited build in the export view.

To perform the required build:

Register and set the export view on your workstation, which is an HCL VersionVault host:
```
cleartool mktag -tag libpub_expvu /public/export.vws 
cleartool setview libpub_expvu
```
Build in the normal way, on your host:
```
cd /proj/libpub
clearmake
```

The preceding listed script specifies a particular non-VersionVault host, titan, on which remote shells are to be executed. If builds are performed on more than one non-VersionVault host, you must generalize this script.

Note: Because the remote host name is a part of the build script, winkin of derived objects built on the various hosts fails unless you make further modifications (for example, by using clearmake -O to disable build-script checking).