IC Installation $PATH?

[Erik Wanta]

What are the minimum UNIX environment settings for IC? The
installation manual says to just set PATH to .../tools/bin. I notice
that in .../tools/bin it has symbolic links to other directories
(example spectre). I also notice that some binaries are missing
(example wavescan, techLoadDump, vcc, watch, wdd, xcam, xcolors ...).
Should I be concerned that the list of binaries in .../tools/bin is
not a complete list of binaries?

Do I need to set LD_LIBRARY_PATH?

Do I need to set CLASSPATH?

Is just CDS_LIC_FILE and PATH required? Can I use LM_LICENSE_FILE
instead of CDS_LIC_FILE?

---
Erik

 

[Bernd Fischer]

Add to the UNIX PATH variable <install_dir>/tools/bin and
<install_dir>/tools/dfII/bin. Add to the UNIX LD_LIBRARY_PATH
variable <install_dir>/tools/lib.

LM_LICENSE_FILE is in my opinion a default variable
for Flexlm which can also be used by other software
vendors than Cadence, so use CDS_LIC_FILE to prevent
confusion.

Bernd


Erik Wanta wrote:

What are the minimum UNIX environment settings for IC? The
installation manual says to just set PATH to .../tools/bin. I notice
that in .../tools/bin it has symbolic links to other directories
(example spectre). I also notice that some binaries are missing
(example wavescan, techLoadDump, vcc, watch, wdd, xcam, xcolors ...).
Should I be concerned that the list of binaries in .../tools/bin is
not a complete list of binaries?

Do I need to set LD_LIBRARY_PATH?

Do I need to set CLASSPATH?

Is just CDS_LIC_FILE and PATH required? Can I use LM_LICENSE_FILE
instead of CDS_LIC_FILE?

---
Erik

 

[John Gianni]

Bernd Fischer <bernd.fischer@xignal.de> wrote in message news:<40B1C0B1.7010508@xignal.de>...

Add to the UNIX PATH variable <install_dir>/tools/bin and
install_dir>/tools/dfII/bin. Add to the UNIX LD_LIBRARY_PATH
variable <install_dir>/tools/lib.

I'm not sure of exactly what's needed, as a bare minimum, and
I'm sure Erik & Bernd are well aware of this, but, for the
general populace, I remind all to no longer set:
$CDS_INST_DIR

This recommendation has a long history, which basically
boils down to Cadence software has recently been modified
to set this by itself, no matter what you do in your
personal shell environment (it will ignore your entry).

On the original topic, a quick look at my DFII path shows
these binary directories Erik can consider adding:
`cds_root icfb`/tools/bin
`cds_root icfb`/tools/DFII/bin
`cds_root icfb`/tools/plot/bin
`cds_root icfb`/tools/leapfrog/bin
`cds_root icfb`/tools/dracula/bin

And, I also see the following shell environment variables
which may be of interest to the user to consider when
compiling the bare minimum needed:

Licenses:
LM_LICENSE_FILE = ...
5280@machine.domain.com:
5280@machine.domain.com:
...
CDS_LIC_FILE = $LM_LICENSE_FILE

Manpages:
MANPATH = ...
`cds_root icfb`/tools/man:
`cds_root icfb`/share/man:
...
Modules:
LD_LIBRARY_PATH = ...
`cds_root icfb`/tools/lib:
`cds_root icfb`/tools/verilog/lib:
`cds_root icfb`/tools/leapfrog/lib:
...
LIBPATH = ...
`cds_root icfb`/tools/lib:
`cds_root icfb`/tools/verilog/lib:
`cds_root icfb`/tools/leapfrog/lib:
...
SHLIB_PATH = ...
`cds_root icfb`/tools/lib:
`cds_root icfb`/tools/verilog/lib:
`cds_root icfb`/tools/leapfrog/lib:
...
Settings:
CDS_Netlisting_Mode=Analog

Also, in the official Cadence .cshrc file,
it never runs "set path = $PATH"; instead it always
sets variables which are then used to set the path.

On your specific questions of:

Do I (really) need to set LD_LIBRARY_PATH?
Do I need to set CLASSPATH?
Isn't just CDS_LIC_FILE and PATH required?
Can't I use LM_LICENSE_FILE instead of CDS_LIC_FILE?
I'll see if I can get an answer from an expert to you

(via your company email).

John Gianni
--
Everything said here is PERSONAL OPINION; none are company sponsored.

 

[John Gianni]

On your specific questions of:
Do I (really) need to set LD_LIBRARY_PATH?
Do I need to set CLASSPATH?
Isn't just CDS_LIC_FILE and PATH required?
Can't I use LM_LICENSE_FILE instead of CDS_LIC_FILE?
I'll see if I can get an answer from an expert to you
(via your company email).

I forwarded this to Erik's company email
(I don't email to non-professional addresses) ...

One set of suggestions revolved around using the Cadence
Stream Manager, which is shipped with every CDROM from
Cadence.

The other set of suggestions basically backed up what
Erik had already figured out, for example:

From: JS
Subject: Re: Minumum DFII settings (e.g., CLASSPATH?)
To: John Gianni

Hello John,

AFAIK,

Eric is right about minimum required configuration for IC tools.

setenv CDSHOME /path/to/cds_installation
set path=( $CDSHOME/tools/bin $CDSHOME/tools/dfII/bin )
setenv CDS_LIC_FILE <port>@<hostname>

I prefer use of CDS_LIC_FILE over LM_LICENSE_FILE, as it has higher
precedence and it's Cadence specific. LM_LICENSE_FILE, at the same
time, is used by every other vendor.

License variable is also not required:
1. If the information is already there in the clients file.
$CDSHOME/share/license/clients
2. If license file is called license.dat and it is in
$CDSHOME/share/license/license.dat

Unix related variables Eg. LD_LIBRARY_PATH, CLASSPATH, SH_LIB_PATH
etc. are generally not required unless:
1. You are already setting them to some value.
2. You have a custom installation.

This is all to get you going with IC tools.

More mandatory variables kick in, when you are using multiple streams,
ASSURA with IC, or AMS with IC, etc.

Then you have to specify variables like:
ASSURAHOME, AMSHOME, etc.

Hundreds of other variables are only for further customization to suit
some specific needs.

Thanks.
-JS