Stats

  • Locked Locked
  • Replies 12
  • Subscribers 125
  • Views 9281
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

CSF search mechanism - load .cdsinit from $HOME even if its disabled in setup.loc

HoWei

I have read the article "Cadence Application Infrastructure User Guide IC6.1.7" to understand the CSF search mechanism. Whilst playing around with the settings, I found that it still loads the ".cdsinit" from $HOME, even if I explicitly did exclude/comment this location in "setup.loc".

In my workarea, the following files are used:

setup.loc:                only "." is enabled as search-location, all others are commented

csfLookupConfig:   only "NONE" is set

For my understanding, the above settings should result in not loading any .cdsinit. But I clearly see that the ~/.cdsinit is loaded (by printing a dedicated message into CIW). I am using ic6.1.7.500.1400.

# cdswhich -lookupconfig .cdsinit
Info (cdswhich): Cadence software is not configured to locate
                 file '.cdsinit' via Cadence Search File mechanism

Question1: Why does virtuoso load the ~/.cdsinit ? 

Another thing I did not clearly understand from the above mentioned article, is the requirement for the "csfLookupConfig" file. According to my tests it might be enough to have "cfsLookupConfig" in my workarea to define what file to load via CSF.

Question2: Do I need to have this file in all locations defined in setup.loc, or is it enough to just have it in my workarea (which is the first search location in setup.loc) ?

Rgds.

Holger

  • HoWei
    in reply to HoWei

    I found that the following code is doing what I need:

    when(  isFile(".cdsinit_personal") loadi(".cdsinit_personal"))

    when(  isFile("~/.cdsinit") loadi("~/.cdsinit"))
    when(  isFile("~/.cdsinit_personal") loadi("~/.cdsinit_personal"))

    As said - I need to give the locations explicitely.

    Do you see any issue with this ?

  • Andrew Beckett
    in reply to HoWei

    Should be fine - you only need to make sure you don't  end up in a loop - probably wouldn't. I might be tempted to make the first one use "./.cdsinit_personal" (in both the isFile and loadi) to make sure that you don't accidentally load the wrong file if the SKILL path doesn't include "." at the beginning (isFile and load/loadi use the SKILL path - getSkillPath() to resolve local file names).

    Andrew.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.