Page History

...

1. Set your login to point to the Cadence license server
   
   

   Code Block
   language bash
   $ setenv CDS_LIC_FILE 5280@<hostname>

   using the hostname you are given by CNF staff.
   
   

2. Set your login to point to the Cadence install location (example for IC618):

   Code Block
   language bash
   $ setenv CDSHOME /opt/local/cadence/installs/IC618 $ setenv PATH ${PATH}:/opt/local/cadence/installs/SPECTRE191/bin:/opt/local/cadence/installs/IC618/bin $ rehash

   The above command may be different for other Cadence subproducts.
   
   

3. Create a folder in your home directory to store your custom cadence libraries/circuits. We'll simply call this folder "cadence"
   
   

   Code Block
   language bash
   $ mkdir ~/cadence

4. Create an initial cds.lib file in your home directory. Your initial file should contain the following:
   
   

   Code Block
   SOFTINCLUDE /opt/local/cadence/installs/IC618/share/cdssetup/cds.lib SOFTINCLUDE /opt/local/cadence/installs/gpdk180_v3.3/cds.lib.oa22 DEFINE <my_first_library_name> ~<my_username>/cadence

   substituting your netid or guestid for " <my_username> " ... make sure to include the '~' character . And substituting a library name for " <my_first_library_name> ".
   
   While cadence does have a GUI library editor, things will work better if you first create the cds.lib file with the above.
   
   The above lines are for the IC618 and GPDK cadence products. For other cadence products, you may need additional "SOFTINCLUDE" lines.

...