• 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 Design
  3. How do I automatically load bindkeys every time I open Virtuoso...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 128
  • Views 23860
  • 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 do I automatically load bindkeys every time I open Virtuoso?

Unicode787Plus
Unicode787Plus over 16 years ago

For some reason, whenever I open Virtuoso in my school's UNIX/Linux account, bindkeys are not automatically enabled (except Esc to cancel a command). My only manual workaround is by typing the following on the CIW:

load(prependInstallPath("samples/local/leBindKeys.il"))

How do I set up my account to automatically load bindkeys?

  • Cancel
  • archive
    archive over 16 years ago

    You can set commands to run automatically by creating a .cdsinit file, as described in <install_dir>/doc/dfIIconfig/dfIIconfig.pdf

    Essentially, just add the line to .cdsinit in your home directory or the current directory.

    Cheers,

     Roger

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stuso
    stuso over 16 years ago

    Hi there,

    Are you using the sample cdsinit file from cadence? If you open your the equivalent of this file:

     ...../IC06.13.507/tools.lnx86/dfII/samples/local/cdsinit and search for bindKey you will find it should be referenced.

    If i remember correctly the first place cadence will look for a .cdsinit will be:

     IC06.13.507/tools.lnx86/dfII/local

    Do you have such a directory, i suspect you do not or it is empty? I had to create mine and then copy the sample cdsinit to .cdsinit, for example:

    cd  /IC06.13.507/tools/dfII

    mkdir local

    cd local

    cp  /IC06.13.507/tools.lnx86/dfII/samples/local/cdsinit .cdsinit

    Note that you can still have your own .cdsinit & .cdsenv in your working area to setup your own particular preferences.

    Hope this helps

    Stu

     

     

     

     

     

     

     

     

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 16 years ago

     Hi,

     I will add to what Stu has said. The first .cdsinit file found by the search mechanism causes that file to be loaded and the search stops, so no more .cdsinit files would be automatically loaded.  However, the samples/local/.cdsinit file could contain SKILL code to load further .cdsinit files, if present. For example:

      when(isFile("~/.cdsinit")
        load("~/.cdsinit")
      )
    

     The .cdsenv files follow a slightly different search methodology in that any files found on the search path will be loaded.  Additionally the environment variable CDS_LOAD_ENV can help to control which, if any, .cdsenv files are loaded, with values like addCWD, CSF, CWD, False, and CWDElseHome. The CSF setting instructs to use the Cadence Search File mechanism.

     I hope that this helps you to set up your environment!

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Deepon Saha
    Deepon Saha over 14 years ago

     

    Thanks Austin,

     

    That reply of yours solved lot of my queries. Helped me a lot in designing a shell script..:)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    Kolkata,

    Austin is where "skillUser" is located. Not his name ;-)

    I've seen a few people making this mistake (as I did intentionally in this reply).

    Andrew (I'm called Andrew, not Bracknell)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Deepon Saha
    Deepon Saha over 14 years ago

    Bracknel,

    Thanks for pointing it out.. ;)

    • 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