John Griessen wrote:
DJ Delorie wrote:
Probably the simplest approach (which I'm leaning towards) is to
treat the netlist file as the target, keep that up-to-date, then let
With the new PCB import code, there's no more netlist file :-O
No more netlist file! :-O Oh Nooooooooooo... :-O
Just kidding, but... This needs to be clarified before John Doty sees
it or ?
Why would that bother me? There's a file that contains netlist
information and more. That happens in other flows, too. Very often some
BOM data makes it into the "netlist".
--
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
[email protected]
_______________________________________________
geda-user mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
