• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. How to load my configeration files from my working directory...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 124
  • Views 17967
  • 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

How to load my configeration files from my working directory not home directory

wgtkan
wgtkan over 12 years ago
How do I load my configuration files (.cdsenv and .cdsinit) from my working directory not the home directory? Because I have multiple design kits and this is creating a bit of confusion. What do I have to do?

Thanks in advance.
  • Cancel
  • skillUser
    skillUser over 12 years ago

    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:

    when(isFile("./.cdsinit")
      printf("Loading .cdsinit from current directory %s\n" getWorkingDir())
      load("./.cdsinit")
    )
    

    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.

    Best regards,

    Lawrence

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • wgtkan
    wgtkan over 12 years ago

     Do I write that in .cdsinit file?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 12 years ago
    Which bit?  The [when(isFile...] part is SKILL, so that would go in a .cdsinit file, such as the site .cdsinit file <if any>.  The setenv staement is for setting a Unix environment variable and therefore can go in your terminal or .cshrc (or similar if using a shell other than 'csh').
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • wgtkan
    wgtkan over 12 years ago

     

    Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:8.0pt; mso-para-margin-left:0in; line-height:107%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}

    I copied: when(isFile("./.cdsinit")

      printf("Loading .cdsinit from current directory %s\n" getWorkingDir())

      load("./.cdsinit")

    )

    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

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information