• 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. can we use unix enviorment variables in stream in deck file...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 142
  • Views 12969
  • 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

can we use unix enviorment variables in stream in deck file ?

archive
archive over 18 years ago

I am new to Skill, Tcl and shell are my scritps language, but there is one thing have no choise but Skill

I use pipo to stream in/out design data

streamInKeys = list(nil
  'libName  "TBD"
....

I'd like to set the lib Name in the Unix shell, just like
setenv cellName TBD

How can we use this user defined variable in the template deck file
I notice that we can get the value of cellName by getShellEnvVar("cellName")
And the question is who can we tell let the tool know the the 'libName is what I set in my shell command line?



Originally posted in cdnusers.org by aidans
  • Cancel
Parents
  • archive
    archive over 18 years ago

    The following syntax will work in the temlate file:

    streamOutKeys = list(nil
    'runDir "."
    'libName "mylib"
    'primaryCell getShellEnvVar("CELLNAME")
    'viewName "layout"

    -Derek


    Originally posted in cdnusers.org by dmay
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    The following syntax will work in the temlate file:

    streamOutKeys = list(nil
    'runDir "."
    'libName "mylib"
    'primaryCell getShellEnvVar("CELLNAME")
    'viewName "layout"

    -Derek


    Originally posted in cdnusers.org by dmay
    • 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