Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Linux and UNIX
Working with DOs and configuration records
You can perform operations on derived objects and configuration records.
Creating links to derived objects
You cannot make a VOB hard link to a derived object, but can make view-private hard links to a derived object.

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.
    - Setting correct permissions for derived objects
      Learn how to set permission for derived objects.
    - Listing and describing derived objects
      Learn how to list and describe derived objects.
    - Identifying the views that reference a derived object
      The VOB stores information about which views reference a derived object.
    - Specifying views that can wink in derived objects
      You can use the CCASE_WINKIN_VIEWS environment variable to specify a list of views that can wink in derived objects.
    - Specifying a derived object in commands
      In general, you use standard path names to access DOs when you are working in a view that references them.
    - Winking in a DO manually
      You can manually wink in any DO to your view, using the winkin command.
    - Preventing winkin
      Learn how to prevent winkin to or from your view during a build or audit.
    - Converting derived objects to view-private files
      Using a standard command or program to modify a derived object in any way converts it from a DO to a view-private file.
    - Working with DO versions
      Learn how to create DO versions and check in DOs during a build.
    - Converting nonshareable DOs to shared DOs
      To convert a nonshareable DO to a shared DO, use the winkin command.
    - Creating links to derived objects
      You cannot make a VOB hard link to a derived object, but can make view-private hard links to a derived object.
    - Displaying VOB disk space used for derived objects
      The dospace command reports VOB disk space used for shared derived objects.
    - Derived objects environment variables
      Learn about the environment variables of the derived objects.
    - Deleting derived objects
      The rmdo command removes the data container and the VOB database object for a derived object.
    - Displaying contents of configuration records
      The catcr command displays the contents of a configuration record.
    - Comparing configuration records
      Because configuration records provide complete records of how DOs are built, you can use them to determine how two builds differ.
    - Attaching labels or attributes to versions in a CR
      You can attach a label or an attribute to the versions in the CR hierarchy of a derived object.
    - Configuring a view to select versions used to build a DO
      To select the versions in the CR hierarchy of a derived object, use the -config version selector in the config spec of your view.
    - Including a makefile version in a configuration record
      Learn how to include a makefile version in a configuration record.
  - 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

Creating links to derived objects

You cannot make a VOB hard link to a derived object, but can make view-private hard links to a derived object.

You can make one or more view-private hard links to a derived object, using the UNIX or Linux ln command, with these restrictions:

The derived object must be visible in the dynamic view where the view-private hard link is to be created; that is, it must appear in a standard UNIX or Linux ls listing. (You can use the winkin command to satisfy this requirement.)
The path name of the hard link must be within the same VOB as the original derived object.

All hard links to a derived object, including the name under which it was originally created, appear with the same DO ID in an HCL VersionVault ls listing; if there are multiple names for a derived object in the same directory, all are listed. For example:

% ln hello hw

% cleartool ls

...
hello@@19-May.19:15.232
hw@@19-May.19:15.232
...

In a catcr or describe command, you can reference a derived object using any of its hard links; all the references are equivalent. But an lsdo command must reference a derived object by its original name, not by any of its subsequently created hard links. Likewise, a derived object can be winked in only at its original path name.

Special case: If a hard link is created by the same build script as the derived object itself, the hard link becomes an additional name for the DO. lsdo lists the hard link, and clearmake can wink in using the hard link's path name.

Each additional hard link increments a derived object's reference count. An lsdo -l listing includes the reference counts and the dynamic views in which the references exist. The (2) in this example shows that view old.vws has two references to hello:

% cleartool lsdo -long hello 
08-Dec-03.12:06:19 Chuck Jackson (test user) (jackson.dvt@oxygen)
 create derived object "hello@@08-Dec.12:06.234"
 references: 2 => oxygen:/usr/vobstore/tut/old.vws (2)