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

Parents
  • Andrew Beckett

    Hi Holger,

    The default behaviour of .cdsinit is that it is searched for in <ICinstDir>/tools/dfII/local, then the working dir and then the home dir (this mechanism predates the CSF mechanism, so it needed to be preserved as the default). It only uses CSF if you enable CSF (via the csfLookupConfig) and even then if it fails to find a .cdsinit using the CSF mechanism, it will continue to search using the standard (default) method.

    So to answer your questions:

    1. Because there is no "INCLUDE .cdsinit" in your csfLookupConfig, it looks in tools/dfII/local then working dir then home. Even if you did have the INCLUDE line in the csfLookupConfig, and just had "." in the setup.loc, it would still find it because no .cdsinit was found via the setup.loc locations. Note you can always do "virtuoso -nocdsinit" if  you don't want the cdsinit loading at all.
    2. The csfLookupConfig is searched for in the setup.loc locations. In fact the setup.loc file is also searched for using the CSF mechanism. Commonly people define $CDS_SITE as a directory containing csfLookupConfig and setup.loc so you can customise it yourself.

    Regards,

    Andrew.

  • HoWei
    in reply to Andrew Beckett

    Thanks Andrew for - Question1 is now clear.

    For Question2 I still do not understand if I "need" it in all locations, or if it just takes the first "csfLookupConfig" found and looks for all files defined in this first "csfLookupConfig".

    Can you elaborate more on that ?

Reply
  • HoWei
    in reply to Andrew Beckett

    Thanks Andrew for - Question1 is now clear.

    For Question2 I still do not understand if I "need" it in all locations, or if it just takes the first "csfLookupConfig" found and looks for all files defined in this first "csfLookupConfig".

    Can you elaborate more on that ?

Children
  • Andrew Beckett
    in reply to HoWei

    Ah, sorry. It uses just the first csfLookupConfig it finds. There is the ability to LOAD another file from within the csfLookupConfig (with a different name) - and that included file (we have to use the word LOAD as INCLUDE is already used for another meaning) is also searched for using the CSF mechanism (and again, only finds the first file). I've probably just over-complicated things now!

    Andrew.

  • HoWei
    in reply to HoWei

    Okay, at least my question is solved. I might once check this overcomplicated mechanism with "LOAD" as well.

    Thanks !

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.