By default the tools will look in the current directory for a .cdsinit file, but if one was found earlier in the search path, that one would have been loaded and the search stops (i.e. the first one found is loaded) - if this is the case then that file could include a statement to load a ./.cdsinit if present, something like:
printf("Loading .cdsinit from current directory %s\n" getWorkingDir())
For the .cdsenv file there is an environment variable that controls the loading, you would want a setting that includes the current directory:
setenv CDS_LOAD_ENV addCWD
[valid values are False, CWD, addCWD, CWDElseHome and CSF]
So your choice depends on whether you wish to find and load other .cdsenv files and in which order (e.g. "addCWD" would load the current directory .cdsenv after a ~/.cdsenv file).
The "CSF" choice is the Cadence Search Facility - look this up in the documentation, it affects the search paths and order of many setup files.
Hopefully this helps you.
In reply to skillUser:
Do I write that in .cdsinit file?
In reply to wgtkan:
/* Style Definitions */
mso-padding-alt:0in 5.4pt 0in 5.4pt;
I copied: when(isFile("./.cdsinit")
printf("Loading .cdsinit from current
directory %s\n" getWorkingDir())
Into the .cdsinit file.
I also set the environment so that .cdsenv get loaded from my
current directory. It doesn’t seem to work. I have 2 PDK’s in two different
working directories with their respective configuration files (.cdsenv and
.cdsinit) but for some reason when I start a new cadence session .cdsenv is
loaded from the home (root) directory.
How do I fix this issue?
Thank you very much