Mail Archives: geda-user/2014/07/09/13:05:25
Dave Curtis wrote:
>
> A friend across town has been using KiCad for a while, and since we
> are interested in building the same sorts of things we try to share
> what we can in terms of tools and designs. Right now, we are hot on
> the "grand, unified, footprint generator script" problem. We would
> like to come up with a single front-end that can create footprints for
> both pcb and KiCad so that we could share footprints more easily.
> So... I've been looking at the KiCad footprint file format and their
> new one can handle a lot of things that are somewhat vexing in pcb --
> although I'm not too hot on the S-expression idea overall. Anyway,
> KiCad seems to leave some things out that my friend and I have been
> talking about -- like keep-outs.
>
> So the point of the above paragraph is, yes, I can suggest some
> extensions, and now would be a good time to capture that since I am
> trying to wrap my head around the issues right now. What I can do:
>
> 1. write up some straw-man spec extensions
> 2. update the "footprint creation for.." document with what ever
> settles out of that.
>
> What I can not do:
>
> Investigate the feasibility of implementing the extensions. I simply
> don't know the code well enough.
>
> -dave
>
>
Hi Dave,
Please have a look at:
https://github.com/bert/fped
It was a parametric footprint editor just for generating KiCad footprint
libraries until I added code for generating pcb footprints.
I got stuck at the point of separating the individual footprints for pcb
(for KiCad a library of concatenated footprints is generated).
Please give it a test drive, patches are welcome :)
Kind regards,
Bert Timmerman.
- Raw text -