• 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. Get current script directory

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 17440
  • 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

Get current script directory

useratcad
useratcad over 16 years ago

Hello,

I need to find the current dir of the loaded skill file to automatically load the other files in the folder.

I found that  "get_filename(piport)" will return the skript name, but not the dir.

How could I do that? 

 

Thanks Tim 

  • Cancel
  • skillUser
    skillUser over 16 years ago

    Hi Tim,

    Using your idea of get_filename(piport), I have expanded it a little to obtain the root of the directory name.

    This seems a little clunky, and I have only tested it under a couple of conditions, but it seemed to work:

    when(file = get_filename(piport)
     ;; expand the file using the SKILL path
     matches = foreach(mapcar path getSkillPath()
      when(isFile(strcat(path "/" file ))
       simplifyFilename(strcat(path "/" file ))
      )
     )
     full = car(setof(item matches item))
     when(full
      ;; convert the path into a list of strings
      ;; and remove the filename from the list
      path = remd(file parseString(full "/"))
      ;; convert the list of strings back into a
      ;; single string, prepending with "/" for a
      ;; fully qualified path
      root = strcat("/" buildString(path "/"))
      ;; print and return the file directory root
      printf("root dirname: %s\n" root)
      root
     )
    )

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

    Awesome. I modified it a little and it works perfect. Thanks for your 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