• 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. Limit specific BRD files to only using certain library paths...

Stats

  • State Verified Answer
  • Replies 7
  • Subscribers 160
  • Views 6248
  • Members are here 0
More Content

Limit specific BRD files to only using certain library paths?

bengelJF
bengelJF over 1 year ago

I'm repackaging an existing design from an outside group and have received a schematic and footprint/padstack files.

By pure coincidence, some of the footprint names in the schematic matched up with our internal libraries and were placeable in the board file straightaway. However, I don't want this file to be able to access our internal libraries; I want it to only pull from a particular project-specific library.

I hop between projects pretty regularly, so I don't want to delete everything from my padpath and psmpath to limit my entire installation to the project-specific library. If I do this, I'd have to change them every time I hop to a different board, which could be multiple times a day.

Is there a way to tell a board file to only use specific libraries/file paths?

  • Sign in to reply
  • Cancel
Parents
  • John T
    +1 John T over 1 year ago

    Hi bengelJF, it is possible to place a brief SKILL file inside each design folder; in this file you can rewrite the library paths automatically when the design is opened. 

    This SKILL file is to be located in the same folder as your brd design, place the following lines of text in this; alter to suit your desired library paths:

    axlSetVariableFile("psmpath" "C:/SPB_Data/Lib/symbol" )
    axlSetVariableFile("padpath" "C:/SPB_Data/Lib/pad" )

    Save the above in a file named LibraryPaths.il as example.

    To complete the automation, go to your allegro.ilinit file located in the folder %home%/pcbenv. This SKILL initialisation file runs upon opening your design, therefore we should add the following line of code to allegro.ilinit : 

    load("LibraryPaths.il")

    In this way, any design can have specific individual paths loaded directly upon opening the board. Each design folder can have a different library path due its own version of the  LibraryPaths.il file. 

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • bengelJF
    0 bengelJF over 1 year ago in reply to John T

    I'll verify this as the answer since it's a good way to handle it through scripting. For those reading in the future, we came up with a way to handle this without scripting; see my response below.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • bengelJF
    0 bengelJF over 1 year ago in reply to John T

    I'll verify this as the answer since it's a good way to handle it through scripting. For those reading in the future, we came up with a way to handle this without scripting; see my response below.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • 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