Re: [Kicad-developers] Reading eagle's lbrs directly

2016-04-09 Thread Daniel Wilches
With .lbr file I meant what Benjamin Nauck explained above. A file that has 4 things: the layout of physical pads of components' pads for the PCB, the schematic of the component, the mapping of physical pads to schematic pins and some metadata. For example, a device looks like this (pin mapping n

Re: [Kicad-developers] Reading eagle's lbrs directly

2016-04-08 Thread Wayne Stambaugh
On 4/8/2016 8:55 AM, jp charras wrote: > Le 08/04/2016 14:38, Wayne Stambaugh a écrit : >> By lbr file do you mean schematic component libraries or board footprint >> libraries? If you mean component libraries than Nick's comments apply >> and the schematic plugin doesn't exist yet but is part of

Re: [Kicad-developers] Reading eagle's lbrs directly

2016-04-08 Thread jp charras
Le 08/04/2016 14:38, Wayne Stambaugh a écrit : > By lbr file do you mean schematic component libraries or board footprint > libraries? If you mean component libraries than Nick's comments apply > and the schematic plugin doesn't exist yet but is part of the current > development cycle. If you mea

Re: [Kicad-developers] Reading eagle's lbrs directly

2016-04-08 Thread Wayne Stambaugh
By lbr file do you mean schematic component libraries or board footprint libraries? If you mean component libraries than Nick's comments apply and the schematic plugin doesn't exist yet but is part of the current development cycle. If you mean footprint libraries, then they have not been implemen

Re: [Kicad-developers] Reading eagle's lbrs directly

2016-04-08 Thread Nick Østergaard
There is some support, we can use the eagle footprints from v6. But the problem I see is simply that it is not easily possible in eeschema yet. 2016-04-08 10:07 GMT+02:00 Benjamin Nauck : > Eagle doesn't store schematic symbols and footprints into separate files > like Kicad does. > Instead Eagle

Re: [Kicad-developers] Reading eagle's lbrs directly

2016-04-07 Thread Nick Østergaard
I guess that lbr files are for the schematic symbols. If that is the case, I think the reason is nothing with licensing, but rather that there is no "plugin" implemented for eeschema as there is in pcbnew, where one would implement this conversion. 2016-04-08 3:28 GMT+02:00 Daniel Wilches : > Hell

[Kicad-developers] Reading eagle's lbrs directly

2016-04-07 Thread Daniel Wilches
Hello, I noticed that to use Eagle's lbr files in Kicad we need to export them from eagle using an ulp (https://github.com/lachlanA/eagle-to-kicad). I think it would be beneficial to have Kicad read directly the lbr files, as that saves time to the user and doesn't require the user to have Eagle.