• 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. Mixed-Signal Design
  3. runams cannot handle environment variables in cds.lib?

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 9392
  • 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

runams cannot handle environment variables in cds.lib?

zdu89
zdu89 over 2 years ago

Hi all,

I found that when I use runams and specify a cds.lib file using the -cdslib option, there will be errors saying the lib-cell-view combination I specified is not a valid cellview.

But the error is gone when I change that library definition with absolute path in cds.lib. And error comes back when I use something like

"DEFINE LIBA $PROJECT_ROOT"

in cds.lib

Is this the limitation of runams or it is me that did not use it correctly?

The runams version I am using is 6.1.8.500

Any input will be appreciated. Thanks

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    There is no version 6.1.8.500 (well, it could be one of 28 different hotfix versions over 4 years - you've missed out the important final part of the version number). However, I'd be rather surprised by this because the -cdslib is something that is pretty central to the virtuoso implementation and has been solid for greater than 25 years. Normally any local path in the cds.lib would be deemed to be relative to the directory containing the cds.lib. 

    Anyway, please provide details of the precise version you're using and then I'll do some checks. I don't want to spend time hunting for a needle in a haystack.

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • zdu89
    zdu89 over 2 years ago in reply to Andrew Beckett

    Hi Andrew, thanks for the reply. The version I am using is 6.1.8.500.15. Sorry for not providing it at first place.

    Since you mentioned that, I will do some experiments with other versions available to me on Monday.

    The error I encountered is not from some relative path like

    "define libraryA ./path/to/lib"

    The error I had was something like this

    "define libraryB $ROOT/$PATH_VARIABLE"

    And this cds.lib file is the same one I use when trying to open Virtuoso GUI and it works fine. Also, I did have those variables defined already and I can see their values when echoing them in the same terminal I ran runams.

    Please let me know the result of your experiments. Thank you!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • zdu89
    zdu89 over 2 years ago in reply to Andrew Beckett

    Hi Andrew, any updates from your check?

    I tried runams6.1.8.-64b.500.27 and still the same issue. Are you able to reproduce what I am describing?

    Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to zdu89

    I tried with ISR15 too (and ISR28) and couldn't reproduce the problem with either version; as I said, I was a little surprised since the -cdslib argument has been supported in Virtuoso and similar applications for a very, very long time - and what you're doing is not that unusual.

    I suggest you contact customer support.

    Andrew

    • 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