Re: RFC: toolenv - for dealing w/ tools' environments

Harlan asks:

> > If tools need their environments intertwingled, it's a
> > fairly static thing.  For Specman, for example, you'd set up
> > 
> >    toolenv specman,vcs,ncverilog,simmagic specman ...
> 
> Is this similar to a configuraiton management "manifest" that says "To do X
> I need the following tools"?

Not quite; more like "If you want to run 'specman' [from the
'specman' package], you'd better have set the CDS_INST_DIR
environment variable."  CDS_INST_DIR is nothing to do with
specman specifically -- it's to do with the 'ncverilog'
package.  Such wacky intertwingling is madness, yes, but
that's the way the EDA world works :-)

Now, if you *are* doing the 'manifest' thing -- "On this
project, we are using specman version 4.1, ncverilog 3.4,
signalscan 6.1, and [so on]..." -- then the above
intertwingling gets a bit more delicate.

With the existing Sidai machinery, I'd do the manifest thing
in my Makefile with (syntax unchecked...):

VERSIONS := specman=4.1 \
            vcs=6.1 \
            ncverilog=3.4 \
            simmagic=3.14 \
            signalscan=6.1

TOOLENV  := ARK_WRAPPERRC="$(VERSIONS)" /our/bin/toolenv

SPECMAN   := $(TOOLENV) specman,vcs,ncverilog,simmagic specman
NCVERILOG := $(TOOLENV) ncverilog ncverilog

%.out : %.in
	$(SPECMAN) ....

(Something tells me I'm just confusing everyone.)

Will


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com