Conference smurf::buildhelp

1127.0. "supportos pools now have links to .nightly/obj,export" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Dec 13 1994 19:37

Date Of Receipt: 	29-NOV-1994 17:50:11.05
From: 	ALPHA::jmf "Joshua M. Friedman OSF/UNIX SDE  29-Nov-1994 1744"
To: 	useg@DEC:.zko.alpha
CC: 	metsch@DEC:.zko.alpha, odehelp@DEC:.zko.alpha
Subj: 	supportos pools now have links to .nightly/obj,export

USEG developers, all of the submit pools (v*supportos with no suffix)
are source-only pools.  This pool is not the result of a build, and so
there are not any exports or objs.  This has always been structured
this way.

In order to build against a fully populated tree which has consistent
sources and exports and objs, you need to back your sandbox to the
v*supportos.nightly tree, not the submit tree.

Sometimes, to test against new submits, it may be necessary to build
against the submit tree.  To support this I have done the following,
which is consistent with what is done in the active releases' submit
trees, and it is also how v30supportos was already setup:

Each os submit tree now has a link from obj and export to the obj and
export in the associated ".nightly" tree.  These would be the closest
built obj and export images to what would be in sync with the submit
tree, however, recognize that it is out of sync once a submit is done
after the last good build.

If you plan to build when backing to the submit tree, <pool>, you will
also have to do the 'odemount' of the appropriate <pool>.nightly.
Eg:
	% cd /usr/sde/osf1/build/v30supportos
	% ls -l export obj
	    export@ -> /usr/sde/osf1/build/v30supportos.nightly/export/
	    obj@ -> /usr/sde/osf1/build/v30supportos.nightly/obj/

	# /usr/sde/odemount v30supportos.nightly

Thank you very much...
				-josh