Stats

  • Replies 14
  • Subscribers 159
  • Views 18875
  • Members are here 0
More Content

Export libraries of all DRA files in specific directory

aricbeaver

Hi,

I would like to use SKILL to iterate through every single DRA file in a directory and export the libraries, i.e. padstacks, shapes, etc. The reason is to verify library contents during each library commit.

Would this be the proper way to do this?

1. Get the DRA file paths using getDirFiles(<directory>)

2. Open DRA file

3. Use axlShell(<command>) to open export library form

axlShell("dlib")
axlShell("setwindow form.dlib")
axlShell("FORM dlib destination export")
axlShell("FORM dlib execute")

4. Repeat 2-3 for every other DRA file

Thx,

Aric

Parents
  • Hey Dave,

    Thanks for the reply. Where is the reference manual for the available skill functions? I only have PCB Editor installed not the custom IC stuff. I keep reading about this "skill finder" application but it only relates to custom IC software I think.

    Yes! Some example code would be great. I found this since you mentioned the axlWritePackageFile function, looking into this now.
    community.cadence.com/.../37080

    Also, curious why you say "if you really want to do this". In my experience it is difficult to manage a collaborative version control repository of Cadence library components. Exporting the contents (padstack/shapes/etc) from the DRA seems like the best way to approach implementing a "change control committee" process.

    Thx,
    Aric
Reply
  • Hey Dave,

    Thanks for the reply. Where is the reference manual for the available skill functions? I only have PCB Editor installed not the custom IC stuff. I keep reading about this "skill finder" application but it only relates to custom IC software I think.

    Yes! Some example code would be great. I found this since you mentioned the axlWritePackageFile function, looking into this now.
    community.cadence.com/.../37080

    Also, curious why you say "if you really want to do this". In my experience it is difficult to manage a collaborative version control repository of Cadence library components. Exporting the contents (padstack/shapes/etc) from the DRA seems like the best way to approach implementing a "change control committee" process.

    Thx,
    Aric
Children
No Data
Cadence Guidelines

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.