• 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. Allegro X PCB Editor
  3. Export libraries of all DRA files in specific directory

Stats

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

Export libraries of all DRA files in specific directory

aricbeaver
aricbeaver over 8 years ago

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

  • Sign in to reply
  • Cancel
Parents
  • eDave
    eDave over 8 years ago
    Hi Aric. It need to run from a board design. It may crash Allegro if the design extents are too small. Try making them huge. Otherwise, you may be finding dra problems causing Allegro to crash. The only suggestion I have for that is to print the name of each dra just before it processes so you know which symbol causes the crash.
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • eDave
    eDave over 8 years ago
    Hi Aric. It need to run from a board design. It may crash Allegro if the design extents are too small. Try making them huge. Otherwise, you may be finding dra problems causing Allegro to crash. The only suggestion I have for that is to print the name of each dra just before it processes so you know which symbol causes the crash.
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information