• 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 SKILL
  3. cdsenv variables

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 12265
  • 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

cdsenv variables

AurelBuche
AurelBuche over 3 years ago

Hi All,

1.

I have seen custom variables in .cdsenv editor (done by external EDA vendors to setup their plugins)

How can I do the same and create custom .cdsenv variables to configure the tools I developed?

2.

I am also wondering, is there a way to find .cdsenv variables documentation?

I find it quite tricky to guess the behavior of each variable only using its name and available values

It is also a pain to find the exact variable answering to an expected behavior...

(It only works with luck or sometimes there is an article in the online support website or a post on this forum, otherwise I am stuck)

Cheers,

Aurel

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    Hi Aurel,

    This is not that clearly described in the documentation, unfortunately. If you search for "cdsenv registration" in cdnshelp you'll find two sections:

    .cdsenv for Applications (which describes the format of the registration file, but it suggests that it must exist within the IC installation - it doesn't have to)

    Integration Recommendation for EDA Vendors (which is based on an application note/presentation I wrote a few years ago) which talks about having a file toolName.cdsenv found via the setup.loc (Cadence Search File) mechanism. The idea is that the file has to be the same name as your new custom tool, and the tool name in the first column needs to match that. For example, I created a file called mysim.cdsenv with contents like this:

    mysim.envOpts spefFile string "" nil extraComment
    mysim.init remoteDir string "" nil otherComment

    and then I can do envGetVal("mysim.init" "remoteDir")

    Note that the tool name cannot match one of the Cadence existing tool names.

    As for finding documentation, or links from the form to the cdsenv, there's no consistent way of doing this (history, I'm afraid).  The best you have is keyword searching for the variable name. I've been pushing for a better way of doing this, but it's not an overnight task.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • AurelBuche
    AurelBuche over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    Sorry for the late response

    Thanks for your anwser, I will use the integration part Slight smile

    Sadly the cdsenv variables don't have a regular documentation structure just as I feared

    Have a nice day

    Aurélien

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • AurelBuche
    AurelBuche over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    Sorry for the late response

    Thanks for your anwser, I will use the integration part Slight smile

    Sadly the cdsenv variables don't have a regular documentation structure just as I feared

    Have a nice day

    Aurélien

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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