Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Windows
Working with DOs and configuration records
You can perform operations on derived objects and configuration records.
Winking in a DO manually
You can manually wink in any DO to your view, using the winkin command.

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.
    - 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're 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.
    - Displaying VOB disk space used for derived objects
      The dospace command and the VersionVault Administration Console report 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 config 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 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
    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 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.

Winking in a DO manually

You can manually wink in any DO to your view, using the winkin command.

For example:

Z:\vob_hw> cleartool lsdo hello.exe
08-Mar.12:48   akp        "hello.exe@@08-Mar.12:48.265"
07-Mar.11:40   george     "hello.exe@@07-Mar.11:40.217"

Z:\vob_hw> cleartool winkin hello.exe@@07-Mar.11:40.217
Winked in derived object "hello.exe"

Z:\vob_hw> hello
...

You can wink in a DO that does not match your build configuration for any of the following reasons: to run it, to perform a byte-by-byte comparison with another DO, or to perform any other operation that requires access to the file system data of a DO.

The winkin command can also wink in the set of DOs in a hierarchy of CRs. You can use this recursive winkin to seed a new view with a set of derived objects. For example:

cleartool winkin -recurse x@@20-Jul.14:32.146 
Winked in derived object "\smg_test\file2.txt"
Winked in derived object "\smg_test\file2sub.txt"
Promoting unshared derived object "\smg_test\x".
Winked in derived object "\smg_test\x"

You can use the winkin command to convert a nonshareable DO to a shared DO. If you are using the -recurse option when winking in nonshareable DOs that were not built in the current working directory, you must also use the -adirs option. For more information about using winking in nonshareable DOs, see Converting nonshareable DOs to shared DOs.