• 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. How to EXPORT library's absolute path which defined in cds...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 142
  • Views 1851
  • 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 EXPORT library's absolute path which defined in cds.lib TO bshell variable

Zest
Zest over 6 years ago

I have get a view list like "LIB CELL VIEW"

I wanna see some detail infomation (link/size/property) by using "ls -ltr $LIBPATH/LIB/CELL/VIEW" (the command can be constructed by vim or other txt editor)

How can I get $LIBPATH from current virtuoso enviorment?

=====

#cds.lib in virtuoso start up folder:

include  /PREOJECT/common.lib

#/PREOJECT/common.lib:

DEFINE LIB_ZEST /data/XXX/LIB_ZEST 

I have tried in terminal:

1. echo("$LIB_ZEST ")  -> Undefined variable

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

    ddGetObjReadPath(ddGetObj("LIB_ZEST"))

    You could even find the path to the cellView too by doing:

    ddGetObjReadPath(ddGetObj("LIB_ZEST" "YOURCELL" "YOURVIEW")) ; with appropriate cell and view names of course

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    ddGetObjReadPath(ddGetObj("LIB_ZEST"))

    You could even find the path to the cellView too by doing:

    ddGetObjReadPath(ddGetObj("LIB_ZEST" "YOURCELL" "YOURVIEW")) ; with appropriate cell and view names of course

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Zest
    Zest over 6 years ago in reply to Andrew Beckett

    Problem solved

    Thanks a lot !

    • 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