Re: EAGLE Netlist conversion
From: Virgil Smith (vsmith26_at_comcast.net)
Date: 09/30/04
- Previous message: James Jackson: "Re: EAGLE Netlist conversion"
- In reply to: James Jackson: "Re: EAGLE Netlist conversion"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 30 Sep 2004 03:41:45 GMT
"James Jackson" <JOJ@Texas.net> wrote in message
news:Lr6dnWMPIeNn1MbcRVn-jg@texas.net...
> Virgil,
>
> I took a quick look at the Netlist format that Eagle generates from their
> Schematic.
>
> It has been a whilesince I've used Eagle, and I do not remember if they
have
> multiple Netlist formats to choose from for their Schematic, or if they
use
> scripts to generate the formats.
>
> Anyway... it shouldn't be too difficult to read in the Eagle Schematic
> Netlist and write a 'new' Netlist in almost any format that you would
like.
>
> The Pads Netlist would be easy enough... the EDIF Netlist... not
impossible,
> but a tad more difficult. (I wrote an EDIF Netlist writer for P-CAD 2k,
> which works very well, and is compliant with the EDIF standard.)
>
> Good Luck,
>
> James Jackson
> Oztronics
>
Yeah, that's sorta what I thought -- it shouldn't be too hard to do. I would
just
rather spend my time developing electronics hardware than writing support
s/w.
I get paid for the former, and not for the latter :-)
May I ask what you used to write your netlist conversion package? I would
probably
use C but it seems there will be much parsing of text strings, and if
there's a language
that does it more conveniently, I would like to know.
Thanks for the input,
-vs-
- Previous message: James Jackson: "Re: EAGLE Netlist conversion"
- In reply to: James Jackson: "Re: EAGLE Netlist conversion"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|