Stats

Locked Locked
Replies 4
Subscribers 125
Views 5723
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

Using environment variables in Model Libraries form

I take part in a collaborative design and we are sharing design files in a repository. In order to avoid revising the ADE view everytime we simulate, we would need to define the path to the model libraries using an environment variable.

We have a similar issue with CSV files we use for PWLF sources, but these we solved including them in the repository and using include paths. However, due to IP protection we cannot include the manufacturer libraries in the repository.

We are using ADE XL at the moment but ADE Assembler is also available, would this distinction have any implication in this issue?

Thank you in advance,

José

Parents

Andrew Beckett over 1 year ago

José,

ADE Explorer/Assember both support UNIX env vars on the model libraries form in the same was as ADE XL (and also in the include path - this used not to be the case in the past).

Andrew
Cancel
Vote Up 0 Vote Down

Cancel

Reply

Andrew Beckett over 1 year ago

José,

ADE Explorer/Assember both support UNIX env vars on the model libraries form in the same was as ADE XL (and also in the include path - this used not to be the case in the past).

Andrew
Cancel
Vote Up 0 Vote Down

Cancel

Children

mazorra over 1 year ago in reply to Andrew Beckett

Andrew,
what would the syntax look like? I tried $(VAR_NAME) but that didn't seem to work. Should it be skill getShellEnvVar("VAR_NAME")? Or is there another way?
Cheers,
José
Cancel
Vote Up 0 Vote Down

Cancel
Andrew Beckett over 1 year ago in reply to mazorra

Just use $VAR_NAME/path.scs for example (no parentheses around that variable name).

Andrew
Cancel
Vote Up 0 Vote Down

Cancel
mazorra over 1 year ago in reply to Andrew Beckett

Great, thank you Andrew.
José
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.