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.
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.

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

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.

To standard software (for example, linkers and debuggers), the standard path name of a derived object (util.o) references the DO.

This is another example of HCL VersionVault transparency: a standard path name accesses one of many different variants of a file system object. Note this distinction, however:

A version of an element appears in a dynamic view because it is selected by a configuration specification rule.
A particular derived object appears in a dynamic view as the result of a build or a winkin.

To access a DO in another dynamic view, use a view-extended path name:


/view/drp/vobs/proj/src/msg.o /view/R2_integ/vobs/proj/src/msg.o	(the DO in view drp) (the DO in view R2_integ)

Note: You cannot use view-extended path names in makefiles.

To specify a certain DO in a VersionVault command, use the DO-ID. For example, you can use a DO-ID in the catcr command to view the contents of a config record of a specific DO:

cleartool catcr x.o@@29-Jun.14:40.88

Note: You cannot use a DO-ID in standard commands.

Because DO-IDs can change, avoid using them in files or scripts that operate on a DO. Instead, use a standard path name or the object identifier (OID) of a derived object, which never changes. To determine a object identifier of a DO, use cleartool describe -fmt "%On\n". For example:

cleartool describe -fmt "%On\n" x.o@@29-Jun.14:40.88 
2c5fc68a.2e5311d3.a382.00:01:80:7b:09:69

Also, a derived object is assigned a permanent identifier when it is checked in as a version of an element. For more information, see Working with DO versions.