Mail Archives: geda-user/2015/10/19/23:16:16
John Doty wrote:
> On Oct 19, 2015, at 2:52 PM, Kai-Martin Knaak
> <knaak AT iqo DOT uni-hannover DOT de> wrote:
>
>> IMHO, the missing part in the puzzle is the notion of a "package"
>> which delivers all information specific to a physical component. I
>> deliberately did not write "contain" but "deliver". The package may
>> include footprints viable for this component. Alternatively the
>> package may refer to a footprint library by giving filenames of a
>> footprints known to work. Which of the two is the most appropriate
>> depends on circumstances. Therefore, the choice between inclusion
>> or reference is up to the designer of the library of packages.
>
> But now you’re tangling upstream and downstream. How the footprint
> library works depends on the layout tool.
>
A package provides a way to store all information related to a
specific hardware component. It can be queried/read by any EDA tool.
This includes applications for schematic capture, netlisters, layout
tools, BOM creators, simulation tools, documentation assemblers, 3D
modelers, and whatnot. So the terms "upstream" and "downstream" are
meaningless with regard to the library of packages.
---<)kaimartin(>---
- Raw text -