As of version 1.5.0, the nature of the NCSU CDK installation procedure has changed. The current philosophy is that the CDK should be easy to use as a standalone package by a single user without impact on the site Cadence installation tree.
The steps to install and use the NCSU CDK are now much simpler:
- Un-tar the tar file into a directory. For example: /tmp/x
- Set an environment variable CDK_DIR that points to /tmp/x. For our example with csh or tcsh you would use
setenv CDK_DIR /tmp/x
- Copy $CDK_DIR/.cdsinit (a link to $CDK_DIR/cdssetup/cdsinit) to your home directory or to the working directory in which you want to start Cadence
- If you have a cds.lib file in your home directory or your working directory, add the lines from $CDK_DIR/cdssetup/cds.lib to it. If you don't, copy $CDK_DIR/cdssetup/cds.lib into your home directory or the working directory where you will start Cadence. In either case you can have this cds.lib file include your system cds.lib file by setting the environment variable SYSTEM_CDS_LIB_DIR to point to the directory that holds a cds.lib file you want to include.
Here is an Example installation session.
Of course, if you are using tdm and you want the CDK to be a sitewide entity that all users will use, it is a simple matter to install the tree into your your_install_dir/tools/dfII/local directory. Users will still have to set the CDK_DIR environment variable, and the lines in $CDK_DIR/cdssetup/cds.lib will have to be added to the site cds.lib file. For more information see the Cadence Design Framework II Configuration Guide and the tdm documentation in your Cadence documentation.