Cadence的启动路径

进入Linux系统之后，可以根据需求创建工作目录，创建一个工作目录的目的是可以使设计文件整洁，随着对软件使用的深入，大家会发现每次创建工程，软件都会自动生成相关文件夹，所以在工作目录内操作可以保证即使工程项目再多，工程文件也不至于很乱。

环境配置

Cadence软件的使用涉及到一部分文件配置问题，首先需要注意以下三个文件：
Cadence软件在启动时首先会在启动目录搜索.cdsinit和.cdsenv文件，如果启动目录没有这些文件就会在用户主目录搜索以上文件，最后会在软件安装目录下搜索以上文件，所以为了更好的使用软件最好在Cadence第一次启动前准备好以上文件。

1）cds.lib文件：

该文件是设计库管理文件，包含一些基础设计库定义和用户自定义工程库。可以在工作目录新建cds.lib文件并输入：

SOFTINCLUD <install_dir>/share/cdssetup/cds.lib

2）.cdsinit文件：

包含Cadence的一些初始化设置信息，以及软件的快捷键设置，部分功能和.cdsenv文件重叠。
可以从以下路径：<install_dir>/tools/dfII/samples/local/cdsinit，拷贝到自己的工作目录，并保存为.cdsinit文件。

3）.cdsenv文件：

包含Cadence各种工具的初始化设置信息，部分功能和.cdsinit文件重叠。

启动文件

启动candence有两个十分关键的文件，一个是cds.lib另一个是.cdsinit。

如果使用ic51的时候，使用的是由ic61创建的cds.lib，可能会出错一般而言，在新的文件夹打开cadence，会自己创建cds.lib.如果没有创建，可以自己创建修改

cds.lib文件的定义

• cds.lib文件：cds.lib是配置PDK的文件。include“PDK中cds.lib的绝对路径，可以包含其他的cds.lib，要使cds.lib起作用一定要在cds.lib所在的目录下运行icfb才行。”，该文件是设计库管理文件，包含一些基础设计库定义和用户自定义工程库。可以在工作目录新建文本文件并输入：SOFTINCLUDE /share/cdssetup/cds.lib，文件名保存为: cds.lib.

=========位于MPW（cds.lib）=======================================
# File Created by  at Fri May  5 22:15:39 2017
# assisted by CdsLibEditor
INCLUDE /EDA/cadence/IC616/share/cdssetup/cds.lib

#DEFINE tsmc18 /EDA/PDK/tsmc18pdk/tsmc18
#DEFINE tsmc18_digital /EDA/PDK/tsmc18pdk/tsmc18_digital

DEFINE GSMC_F018Q6D6 /EDA/PDK/GSMC_F018Q6D6_PDK/GSMC_F018Q6D6
DEFINE GSMC_digital_new /EDA/PDK/GSMC_F018Q6D6_PDK/GSMC_digital_new

#DEFINE tsmc35mm_digital /EDA/PDK/tsmc35mm_PDK/tsmc35mm_digital
#DEFINE tsmc35mm /EDA/PDK/tsmc35mm_PDK/tsmc035mm_3d3v_5v_v2d7a_PDK/tsmc35mm
==========位于安装目录下的cdssetup（cds.lib）=====================================
SOFTINCLUDE dfII/cds.lib
SOFTINCLUDE hdl/cds.lib
SOFTINCLUDE pic/cds.lib
SOFTINCLUDE sg/cds.lib


UNDEFINE analogLib /opt/IC617/tools.lnx86/dfII/etc/cdslib/artist/analogLib
DEFINE analogLib /opt/IC617/tools.lnx86/dfII/etc/cdslib/artist/lib_hspice/analogLib

Reference:Cadence Library Path Editor User Guide
The library path editor (cdsLibEditor) enables you to view and edit the information in a cds.lib library definition file.A cds.lib file is needed to point to the reference and design libraries you want to use in your design.
For more information about cds.lib refer to the Cadence Application Infrastructure User Guide.
DEFINE Weng_MPW ./Weng_MPW

Reference: Cadence Application Infrastructure User Guide
To create a new cds.lib file, create an ASCII file named cds.lib in any directory that is listed in your setup.loc file, for example, $HOME.Note: The search order specified in the setup.loc file determines which cds.lib file will be used.为创建新的cds.lib需要该文件包括进setup.loc中。

cds.lib文件三种创建方法

只需要创建新的cds.lib就可以。

可见有三种方式。

创建方法1

为了翻译Cadence各产品之间的，Cadence设计了一种name mapping.名称映射。在应用程序中创建合法名称的规则定义了所谓的名称空间。如下所示，Cadence应用程序之间的数据是可互操作的，因为Cadence将名称从一个名称空间映射到另一个名称空间。名称映射是一致的和可预测的。

创建方法2

创建方法3

位置：在virtuoso的安装目录下的share/cdsssetup/setup.loc中:" /opt/IC617/share/cdssetup

;
; Default setup search locations.
;
; This file is found in the first of the following locations
; that has a setup.loc or cdssetup/setup.loc file:
;
;	.
;	$CDS_WORKAREA
;	$CDS_SEARCHDIR
;	"~" (users home directory)
;	$CDS_PROJECT
;	$CDS_SITE
;	$(compute:THIS_TOOL_INST_ROOT)/share
; 
; Note that for this release we have introduced a new preferred syntax
; to represent a tool's installation root, $(compute:THIS_TOOL_INST_ROOT).
; This syntax is equivalent to the old $CDS_INST_DIR syntax but better
; reflects how the evaluation is done. The old $CDS_INST_DIR syntax is
; still supported in this release, however it may be deprecated in a
; future release. The behavior of $CDS_INST_DIR is unchanged. Please
; remember that $CDS_INST_DIR is not interpreted as an enviroment variable 
; and any such variable is ignored.
;
; The value of $(compute:THIS_TOOL_INST_ROOT) is equivalent to the value 
; of running 
;      cds_root <exe_name>
; (where exe_name is the name of the executable run when the file is read.)
;
; Feel free to make a copy of the default setup.loc file in
; $(compute:THIS_TOOL_INST_ROOT)/share/cdssetup/setup.loc to any of the other locations
; and add additional places to search (e.g. to setup up a site specific
; search list).
; 
; Format: one entry per line, everything after the first blank or
; tab is a comment, ';' or '#' or '--' at the start of a line is a comment.
; $envvar, ${envvar}, ~, and ~user are expanded as needed.
;
; If an environment variable is not defined, then that entry is ignored.
; No errors are generated.
;
.			cwd should always be searched first
@LIBRARY		look in the design libraries for the file
$CDS_WORKAREA		user workarea if defined
$CDS_SEARCHDIR		this is se