jbdavid
|
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
|