Actions
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 176 subscribers
  • Views 288 views
  • Users 0 members are here
Related

Can I simplify my library structure?

Former Member

I have multiple user-created libraries, as I like to organize my library parts by function (all DC-DC converter ICs go in a DC-DC converter library). I find myself making the same parts (SOT23, SOIC8, etc) over-and-over as they show up in many different libraries. Is there a way to have all of these point to a single common_packages library where all of these are defined?

 

I recognize that I can, and do, cut-and-paste packages from library to library but this doesnt help when I want to make a global change to a certain package and have it apply to all, for example, SOIC8s.

 

Thank you!

Sam

Parents
  • 0

    Hi Sam,

    you can collect all the packages you are using in your libraries in a
    simple package library. Similar to EAGLE's ref-packages.lbr.

     

    If you would like to change something in one of your packages, you
    change it in the package library. Now you can transfer the modified
    package into the libraries where you used this package.

     

    -- This can be done with the UPDATE command, for example. Open the
      (target) library where the old definition of the package is used
      and go to Library /Update. The modified package will be integrated
      in your lbr file.

     

    -- You can also use drag&drop for this: Arrange the EAGLE Control
       Panel and the target library editor in a way that you can see both
       simultaneously on the desktop. Now simply drag&drop the modified
       package from the tree view into your library editor window.

     

    -- If you have more than only one or two libraries with packages to
       be updated you could use an ULP for it. There is one named
       run-loop-all-script-lbr.ulp. This ULP executes a script for all
       libraries in the current directory. So we need a script file that
       updates the library files. it can look like this:

     

        UPDATE ref-packges.lbr;

     

       Save this line in a file, for example as  update-lbr.scr.

     

       Now open one of your libraries, start run-loop-all-script-lbr.ulp
       and tell the ULP which script to execute. Now all the lbr files
       in the directory will be updated.

     

     

     

    Hope this helps.

    Regards,
    Richard

Reply
  • 0

    Hi Sam,

    you can collect all the packages you are using in your libraries in a
    simple package library. Similar to EAGLE's ref-packages.lbr.

     

    If you would like to change something in one of your packages, you
    change it in the package library. Now you can transfer the modified
    package into the libraries where you used this package.

     

    -- This can be done with the UPDATE command, for example. Open the
      (target) library where the old definition of the package is used
      and go to Library /Update. The modified package will be integrated
      in your lbr file.

     

    -- You can also use drag&drop for this: Arrange the EAGLE Control
       Panel and the target library editor in a way that you can see both
       simultaneously on the desktop. Now simply drag&drop the modified
       package from the tree view into your library editor window.

     

    -- If you have more than only one or two libraries with packages to
       be updated you could use an ULP for it. There is one named
       run-loop-all-script-lbr.ulp. This ULP executes a script for all
       libraries in the current directory. So we need a script file that
       updates the library files. it can look like this:

     

        UPDATE ref-packges.lbr;

     

       Save this line in a file, for example as  update-lbr.scr.

     

       Now open one of your libraries, start run-loop-all-script-lbr.ulp
       and tell the ULP which script to execute. Now all the lbr files
       in the directory will be updated.

     

     

     

    Hope this helps.

    Regards,
    Richard

Children
No Data