Clearcase中的派生对象 [英] Derived objects in Clearcase

问题描述

我想问清楚ClearCase中的派生对象是什么以及它是如何工作的。

另外我想问是否还有另一个具有相同功能的程序，因为在Git，MKS或IBM®Rational Team Concert™中我找不到类似的东西，是否已经过时了？

解决方案

这与动态视图密切相关，动态视图是ClearCase特有的，在其他最近的VCS中找不到。 p>

请参阅

派生对象（DO）是在使用clearmake或omake进行构建或构建审核期间在VOB中创建的文件。

每个DO都有一个关联的配置记录（CR ），这是DO的物料清单。 CR记录了构建环境，DO的组装过程以及DO的创建所涉及的所有文件的各个方面。

构建工具尝试避免重建派生对象。

• 如果视图中存在适当的派生对象，clearmake或omake会重复使用该DO。


• 如果视图中没有适当的DO，clearmake或omake会在另一个视图中建立现有的DO，该视图可以为眨眼到当前视图。

搜索过程称为购物。

这与非常大的基于C或C ++ makefile的项目有关。

I want to ask what is exactly the derived object in ClearCase and how is work.

Additional i want to ask if there is an other program with the same function, because in Git, MKS or in IBM® Rational Team Concert™ i cannot find something similar, is it obsolete ?

解决方案

This is quite linked to dynamic views, which are very specific to ClearCase and not found in other more recent VCS.

See "ClearCase Build Concepts"

Developers perform builds, along with all other work related to ClearCase, in views. Typically, developers work in separate, private views. Sometimes, a team shares a single view (for example, during a software integration period).

As described in Developing Software, each view provides a complete environment for building software that includes a particular configuration of source versions and a private work area in which you can modify source files, and use build tools to create object modules, executables, and so on.

As a build environment, each view is partially isolated from other views. Building software in one view never disturbs the work in another view, even another build of the same program at the same time. However, when working in a dynamic view, you can examine and benefit from work done previously in another dynamic view. A new build shares files created by previous builds, when appropriate. This sharing saves the time and disk space involved in building new objects that duplicate existing ones.

You can (but need not) determine what other builds have taken place in a directory, across all dynamic views. ClearCase includes tools for listing and comparing past builds.

The key to this scheme is that the project team's VOBs constitute a globally accessible repository for files created by builds, in the same way that they provide a repository for the source files that go into builds.
A file produced by a software build is a derived object (DO). Associated with each derived object is a configuration record (CR), which clearmake or omake uses during subsequent builds to determine whether the DO can be reused or shared.

A derived object (DO) is a file created in a VOB during a build or build audit with clearmake or omake.
Each DO has an associated configuration record (CR), which is the bill of materials for the DO. The CR documents aspects of the build environment, the assembly procedure for a DO, and all the files involved in the creation of the DO.

The build tool attempts to avoid rebuilding derived objects.

• If an appropriate derived object exists in the view, clearmake or omake reuses that DO.
• If there is no appropriate DO in the view, clearmake or omake looks for an existing DO built in another view that can be winked in to the current view.

The search process is called shopping.

This is relevant for very large C or C++ makefile-based projects.

这篇关于Clearcase中的派生对象的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！