Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Build Avoidance or Reuse of Derived Objects

So how does one do Build Avoidance or Reuse of Derived objects
in RTC ? We have option to use RTC or BuildForge builds.

This is a huge system being built on Zlinux or USS. System consists of
C,C++,Assembly. We would like to keep listings, intermediate objects
and reuse the ones whose source hasn't been modified.

Some options could be to..

1. Create an Integration Build Workspace.
Update the search/link path to include this workspace
when doing a local build.

2. Use a combination of Personal Builds with option 1.

One of the requirements is to persist all these derived objects for a
specified period of time and avoid collisions between different builds. This
could make option 2 a problem.

Anyway to get clearmake capabilities into RTC ? Looking forward to any experiences or recommendations.

-Suheb Farooqi

0 votes



One answer

Permanent link
The "Jazz Build Engine" is really a way of invoking a build system, and
collecting its results. So build avoidance or derived object re-use
would be provided by the build system it invokes. The Enterprise
Extensions (provided by the System Z/I RTC extensions do provide
explicit support for build avoidance and derived object re-use on the
Z/I platform. I'll defer comments on BuildForge to a BuildForge expert.

WRT ClearMake, its sophisticated build avoidance and derived object
re-use ("wink-in") depends on the functionality provided by ClearCase
dynamic views. But all Make's provide date-based build avoidance and
derived object re-use, and some provide more sophisticated re-use based
on code dependency analysis scanners (which is what is provided by the
RTC Enterprise extensions).

Cheers,
Geoff

On 9/27/2010 5:37 PM, sfarooqi wrote:
So how does one do Build Avoidance or Reuse of Derived objects
in RTC ? We have option to use RTC or BuildForge builds.

This is a huge system being built on Zlinux or USS. System consists
of
C,C++,Assembly. We would like to keep listings, intermediate objects
and reuse the ones whose source hasn't been modified.

Some options could be to..

1. Create an Integration Build Workspace.
Update the search/link path to include this workspace
when doing a local build.

2. Use a combination of Personal Builds with option 1.

One of the requirements is to persist all these derived objects for a
specified period of time and avoid collisions between different
builds. This
could make option 2 a problem.

Anyway to get clearmake capabilities into RTC ? Looking forward to
any experiences or recommendations.

-Suheb Farooqi

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Sep 27 '10, 5:34 p.m.

Question was seen: 5,481 times

Last updated: Sep 27 '10, 5:34 p.m.

Confirmation Cancel Confirm