Conference smurf::buildhelp

694.0. "ODE s mksb -sub_tree: Great work team!" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Fri Apr 15 1994 15:23

Date Of Receipt: 	15-APR-1994 12:59:27.38
From: 	WASTED::jmf "Joshua M. Friedman ULTRIX SDE  15-Apr-1994 1259"
To: 	decwet::anderson, snow@DEC:.zko.wasted, decwet::ode
CC: 	d_angel@DEC:.zko.wasted, kbaker@DEC:.zko.wasted, meyer@DEC:.zko.wasted,
	tresvik@DEC:.zko.wasted, odehelp@DEC:.zko.wasted, jmf@DEC:.zko.wasted
Subj: 	ODE's mksb -sub_tree:  Great work team!

Tina, Dave, and ODE Team, I wanted to let you know how nice and how
easy to use the mksb -sub_tree environment is to use; from the attached
you can see I've set up the ASE pool to allow kernel building with the
OSF (sterling, gold, ...) environment.

I'd read the stuff in the users guide months ago, and was concerned it
might be complicated to get working, but I just now used the "Back to an
additional (secondary)...." section of the man page and in two seconds
it was done and worked.

Thanks for making this so easy, and, in general, providing excellent
support and a solid, ever-improving, set of tools.

		-josh



If you're interested in some details, read on.

This tree was interesting to get to work because the main ASE tree
needs to inherit all the gold build and export environment, and so ASE
is backed through 'link' to goldos.*, though it's not a shared sb.
It has unique source control information.

It was created with mkrcs and mksubmit; so it's pretty "pure".

The only task left is to move the ase-only kernel files from the 'ase'
rcs tree to be within the 'os' rcs tree, and establish a branch and
perhaps an 'aseos' shared sandbox.


------- Forwarded Message

Return-Path: jmf 
Delivery-Date: Fri, 15 Apr 94 12:39:27 -0400
Return-Path: jmf
Received: from wasted.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/30Mar94-0502PM)
	id AA23058; Fri, 15 Apr 1994 12:39:24 -0400
Received: from longbow.zk3.dec.com by wasted.zk3.dec.com; (5.65/1.1.8.2/01Apr94-1041AM)
	id AA19675; Fri, 15 Apr 1994 12:39:23 -0400
Received: by longbow.zk3.dec.com; id AA22612; Fri, 15 Apr 1994 12:39:22 -0400
Message-Id: <[email protected]>
To: larson, ase_dev
Cc: hsu, tresvik, meg, williams, [email protected], jmf
Subject: How to build ASE kernel files
Date: Fri, 15 Apr 94 12:39:22 -0400
From: "Joshua Friedman, OSF/UNIX SDE 381-1548" <jmf>
X-Mts: smtp

Kernel ASE developers,

To build the kernel piece of the tree, we will use a feature of
ODE which allows backing to multiple things for different 
directories.  You'll get a 'link1' and an 'rc_files1' directory.

NOTE: for right now, check/outs and check/ins won't work on
the ASE kernel files AFTER you make the sub_tree; do your bco's
first and we'll soon get that working.

Do this; for purposes of this example, I've assumed that your
private ase sandbox is called 'ase' (mine is)...

It will prompt you as follows, since, right now, there's a kernel
directory in the ase tree.  This will be moved soon to be part
of the base tree on an ASE branch:

% (whatever shell)
% workon -sb ase
% mksb -back goldos.bl9 -sub_tree kernel -noauto

The sub-directory kernel, already exists in your sandbox, release
Do you really want to overlay this sub-directory?  [no]  y

creating new set: Joshua_Friedman_bld1, setdir: ./kernel


You can now build in the kernel directory as if you're in goldos.bl9.
In fact if you use sbinfo within the kernel directory it looks
completely like your in a sandbox backed by gold.

% cd kernel 
% build   - build the whole kernel tree

or

% mkdir -p kernel/io/common  (this dir. can be empty or only have files
					you're changing)
% cd kernel/io/common
% build	

- -josh

------- End of Forwarded Message