Designer’s Guide Community

asdf

Junior Member

Offline

Posts: 12
Armenia

problem with variable
Nov 24^th, 2005, 10:13pm

I've set $CDS_INST_DIR environment variable to the installation directory of ic5, and used it in cds.lib to define the library analogLib. Whan running ic5 I have no problem, but whan running assura LVS I get the following message:

*WARNING* The directory: '/home/user/assura/tools.lnx86/dfII/etc/cdslib/artist/analogLib' does not exist
but was defined in libFile '.../cds.lib' for Lib 'analogLib'.

but library definition in .../cds.lib is $CDS_INST_DIR/tools.lnx86/dfII/etc/cdslib/artist/analogLib

Why does Assura take another value of variable $CDS_INST_DIR?

Back to top

Bergerak

IP Logged

bernd

Senior Member

Offline

Posts: 229
Munich/Germany

Re: problem with variable
Reply #1 - Nov 25^th, 2005, 6:16am

$CDS_INST_DIR was a kind of reserved variable in 4.4.3
and releases before, I might be wrong here.

From 4.4.5 Cadence recommends not to use this variable any longer
in any login files or in the $PATH variable.
It should be possible to use it in the 'cds.lib', but I personally
never use it.

The problem occurs if you have Cadence tools installed in more than
one installation tree, like DFII and Assura in your case.
Then any tool will evaluate the $CDS_INST_DIR variable and try to
find the libraries in the tools own installation tree.
In your case 'analogLib' in the Assura tree.

Rather than using $CDS_INST_DIR I suggest to use a new variable name
which can not collide with a reserved name.

e.g.

in your login files:
export ASSURAHOME=/<...>/cds/lnx86/assuraoa31_3
export DFIIHOME=/<...>/cds/lnx86/ic5141

in the cds.lib file:
DEFINE analogLib $DFIIHOME/tools/dfII/etc/cdslib/artist/analogLib
DEFINE avTech $ASSURAHOME/tools/assura/etc/avtech/avTech

Bernd

Back to top

Just another lonesome cad guy

IP Logged

jbdavid

Community Fellow

Offline

Posts: 378
Silicon Valley

Re: problem with variable
Reply #2 - Aug 3^rd, 2006, 3:23am

I used Bernd's methodology for years.. but since I don't ALWAYS have assura on my path, and I don't necessarily want to use Envronment variables in the .lib I now use
INCLUDE $(inst_root_with:tools/dfII/bin/icfb)/share/cdssetup/dfII/cds.lib
SOFTDEFINE avTech $(inst_root_with:tools/assura/bin/assura)/tools/assura/etc/avtech/avTech
but I ALWAYS want bmslib - especially when writing models of Hogge phase detectors..
DEFINE bmslib $(inst_root_with:tools/dfII/bin/icfb)/tools/dfII/samples/artist/bmslib

nicely with the SOFTDEFINE
if I don't have assura on my path, I don't get any complaints because its not there..

the $CDS_INST_DIR methodology broke down so bad in 1999, as many people were using cadence tools from
many installation hierarchies EACH of which assumed $CDS_INST_DIR was set to THEIR hierarchy.. that
they stopped using it.. - for a while they allowed it in the .lib files, but
it was explicitly mentioned that any cadence tool interprets it as its own installation directory, and
totally ignores any environment variable definition for CDS_INST_DIR even if you did set it..
so if you STILL use it, assura assumes its pointing to its own installation, but the library you want only exists in the IC installation..
the methods above are documented in the cadence manuals and works for ALL tools since 446 days.
It exams your executable path, to find the icfb executable.. calls cds_root to find the "tools" dir that contains it.. and then prepends that to the rest of the path string..

Hope this helps

Back to top

jbdavid
Mixed Signal Design Verification

IP Logged