Conference smurf::buildhelp

Date Of Receipt: 	20-SEP-1995 16:05:38.89
From: 	SMURF::FLUME::johnf "John Flanagan USG Test Johnf Tools Group  20-Sep-1995 1603"
To: 	"Wayne Casagrande, USG Performance Engineering" <wayne@DEC:.zko.flume>
CC: 	[email protected], odehelp@DEC:.zko.flume, vandyck@DEC:.zko.flume,
	johnf@DEC:.zko.flume
Subj: 	Re: Question on new ODE and bcscope

	1) Can I still create and play with sandboxes for the various
	releases without obtaining a principal from each of the release
	project leaders.  I hope this is not the way it will have to work - 
	since it would be a real hindrance.

Use the -nk switch with workon.  This will do what you want [it allows you to
do a workon in which you don't intend to perform bco/bci/bsubmit].

	2) Am I really required to workon a specific sandbox before
	doing a cscope?  I notice that the cscope databases have dissappered
	and I am stuck at the moment.

The following mail message may address #2:

>If you use bcscope, you don't need to do this, but if you'd rather use cscope 
>directly, you can access it like this. Define cscope in your environment:
>
>setenv CSCOPE "/usr/sde/osf1/bin/alpha_OSF1/cscope"
>
>then you can access the db like this:
>
>$CSCOPE -P path_to_backingtree -d -f \ path_to_backingtree/logs/cscope/cscope.
kernel
>
>or as in your example:
>
>cd /usr/sde/osf1/build/ptliteos.bl6/logs/cscope
>
>$CSCOPE -P path_to_backingtree -d -f cscope.kernel
>
>In my environment, I define /usr/sde/osf1/build to be BUILD. That would save 
>you some typing. 
>
>Here's something else you may find useful if you use csh.
>
>>I have an alias called setbase;

>>alias setbase 'set ARG=\!:1;source $HOME/bin/setbase.csh'

>and setbase.csh looks like this:

#!/bin/csh
setenv BASE     $BUILD/$ARG
setenv OUTPUT   $BASE/output
setenv LOGS     $BASE/logs
setenv CLOGS	$BASE/logs/cscope
setenv SNAP     $LOGS/SNAPSHOT
setenv BLDLOGS  $BASE/Logs
setenv SRC      $BASE/src
setenv KERN     $SRC/kernel
setenv OBJ      $BASE/obj/alpha
setenv EXP      $BASE/export/alpha/usr


>So that you could do a "setbase ptliteos.bl6" followed by:

>$CSCOPE -P $BASE -d -f $CLOGS/cscope.kernel

>And if you're REALLY lazy, you could alias that whole thing as well, so 
>flipping between trees becomes a question of issuing another setbase command 
>and never having to cd to the right place.




 ______________________________________________________________________

 John Flanagan	 		enet:    [email protected]	
 MS: ZKO3-3/W20			decnet:  flume::johnf
 USG Release Engineering		 (603) 881-1719
 110 Spitbrook Road 			 (DTN) 381-1719
 Nashua, NH  
 ______________________________________________________________________

Date Of Receipt: 	20-SEP-1995 16:34:33.24
From: 	SMURF::ALPHA::"[email protected]" "20-Sep-1995 1632"
To: 	"Wayne Casagrande, USG Performance Engineering" <[email protected]>
CC: 	[email protected], [email protected], [email protected],
	[email protected]
Subj: 	Re: Question on new ODE and bcscope
A two part answer: 	

1) No, you don't need a ticket to do a workon, currently the message from 
workon looks like it's failed, but in fact you are in a workon. You can 
eliminate the noise by doing a workon -nk -sb <sandbox>  
-nk is "no kerberos"

2) I'm working on a non-workon version of bcscope that will work from a menu.


		-Grant

| 
| 
| Hi,
| 
| I have a question regarding ODE V3 and the mail that I have recently seen 
| regarding cscope available as a bcscope tool within the environment.
| 
| I notice that the workon command now requires that I obtain a 
| kerberos principal name before working on a sandbox.  I will not
| be doing submits into any of the pools, but regularly build sandboxes
| to try different performance modifications, etc.  I have 2 concerns/questions
| regarding ode:
| 
| 	1) Can I still create and play with sandboxes for the various
| 	releases without obtaining a principal from each of the release
| 	project leaders.  I hope this is not the way it will have to work - 
| 	since it would be a real hindrance.
| 
| 	2) Am I really required to workon a specific sandbox before
| 	doing a cscope?  I notice that the cscope databases have dissappered
| 	and I am stuck at the moment.
| 
| Thanx,
| Wayne

Date Of Receipt: 	26-MAR-1996 10:28:05.17
From: 	SMURF::WASTED::schloss "Mike Schloss usg  26-Mar-1996 1024"
To: 	buildhelp@DEC:.zko.wasted
CC: 	
Subj: 	bcscope

Is there a man page available for the version of cscope used by bcscope?
It seems much improved over the one that we ship in our SYSV package.

Is the source publicly available?

Mike Schloss

Date Of Receipt: 	26-MAR-1996 11:15:55.20
From: 	SMURF::FLUME::"[email protected]" "Grant Van Dyck  26-Mar-1996 1112"
To: 	[email protected]
CC: 	[email protected], [email protected]
Subj: 	Re: bcscope

| Is there a man page available for the version of cscope used by bcscope?
| It seems much improved over the one that we ship in our SYSV package.

Yes it is, and yes there is one, although until you asked the question, I 
hadn't realized I'd never updated it from the previous version. I just 
submitted it now, so if it isn't on your ode server yet, it will be soon. 
Looks like this in the beginning so you can tell the difference:

root@cardinal [57] odeman cscope
CSCOPE(1)                                                           CSCOPE(1)

NAME
  cscope - interactively examine a C program

SYNOPSIS
  cscope [ options ] [ C source files ]

DESCRIPTION
  Cscope is an interactive screen-oriented tool that helps you:

| 
| Is the source publicly available?
| 

Negative. I tried to get UNX/Locus to get us this version, but didn't get much 
of a response. This version is unsupported and not available publicly.


-- 

				-Grant