[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: gEDA-dev: footprint cleanup
Hi Peter and all,
<snip>
> If gschem2pcb continues to use the M4 library as it exists now (as was
> suggested in one post), we still have to distribute the M4 library,
keep
> it working, and this further difference will be yet another difficulty
> for the user.
Currently gschem2pcb has to handle handle newlib footprints as well, so
dumping m4 footprints doesn't break anything I guess.
<snip>
> What we should strive to have is a generator system where "DIP 8 100
> 300", or whatever, input as a footprint string, will produce the
> required newlib code for the part we want. For users who prefer GUI
when
> not working in batch mode, the generator will provide a GUI to select
> the options I want, piecing together the generator's input string.
What I "read" (after a couple of attempts) is:
1. Convert all the m4 macros to newlib files and reorganize them
(getting a naming convention without flaws and exceptions -->
IPC-7351A++: ask John Luciani about this one).
2. Lose the pcblib part (old m4 index) of the tree in the lib gui.
3. Possibly "obsolete" the m4 macros as in "do not maintain anymore".
The m4 dependency of gschem2pcb will then be obsolete one day (or
gschem2pcb could do without as of now ?).
In a couple of releases it could all be history.
What we possibly need is a footprint generator for the next generation
smd footprints, one that generates newlib files.
Another EUR 0.01
Kind regards,
Bert Timmerman.
_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev