• 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. cdsFinder command not found

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 6710
  • 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

cdsFinder command not found

dietSprunk
dietSprunk over 1 year ago

I'm beginning the SKILL Language Programming Introduction vIC6.1.8 / ICADVM20.1 course and the first command entry doesn't seem to work.

I'm entering cdsFinder & into a terminal window and I'm getting command not found.  Is there a special directory I should be entering this into?

As an aside, I'm able to open the SKILL API Finder through the Virtuoso CIW using both the pulldown menu and the startfinder() command, but I'd like to try to resolve this issue separately, just in case there are other commands that I will need to use in the future that I won't knowingly be able to circumvent through the use of the CIW.

  • Cancel
  • mbracht
    mbracht over 1 year ago

    HI,

    Most likely the directory containing the cdsFinder executable is not in your Unix PATH. The cdsFinder is contained in the tools/bin directory of your IC installation.
    Can you make a 
    % echo $PATH
    ...and see what you get.

    Max

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mbracht
    mbracht over 1 year ago in reply to mbracht

    you also need to have a korn shell (ksh) installed. The cdsFinder is a symbolic link to cdnWrapper which happens to be a ksh script.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to mbracht

    Hi Max,

    The fact that it works with startFinder() suggests that it can be run; most likely dietSprunk's environment is using wrappers around executables (such as virtuoso) and there's no wrapper around cdsFinder...

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • mbracht
    mbracht over 1 year ago in reply to Andrew Beckett

    Hi Andrew...I don't quite understand this - I mean he must have been able to launch virtuoso so tools/dfII/bin must be in the PATH but not necessarily tools/bin. But then again I have to say I never tried to run virtuoso without tools/bin in the PATH.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • dietSprunk
    dietSprunk over 1 year ago in reply to Andrew Beckett

    If I type cds61 into a terminal window, Virtuoso 6.1.8 boots up fine.  Is that the normal command to launch Virtuoso 6.1.8, or is that a wrapper?

    Also, I looked in the bin directory where cds61 exists, but there's no cdsFinder command.  Is this a question that I should be asking my IT department?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mbracht
    mbracht over 1 year ago in reply to dietSprunk

    this is definitely a wrapper - the normal way to launch virtuoso is well...just typing virtuoso

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to mbracht

    Max - it's not unusual for some customers to have a wrapper script (which might even be called "virtuoso" (not in this case, where it's cds61)) which takes care of setting the $PATH, $CDS_LIC_FILE, other things in the environment and then calls the real virtuoso. They may not have the IC installation directly in the path, and so unless a wrapper is provided for cdsFinder too, there's no way to find it...

    cds61 is something provided by your CAD/IT department dietSprunk, so you may want to ask them to provide a way of launching that from a terminal window too.

    Andrew 

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • dietSprunk
    dietSprunk over 1 year ago in reply to Andrew Beckett

    Ok. Will do. Thank you for the help.

    • 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