| delorie.com/archives/browse.cgi | search |
--089e011603f6f567fa0529263fed Content-Type: text/plain; charset=UTF-8 On 12 Jan 2016 17:02, "Frank Miles (fpm AT u DOT washington DOT edu) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote: > > Perhaps I'm confused. I thought I had read that the netlist import was > deprecated, and that the proper way of importing the netlist was through > PCB:File/Import Schematics. If netlist import is still equally valid, > then please accept my apology for the needless noise. > > -F The import mechanism was added as a more integrated way of retrieving this information, rather than relying on an external tool, gsch2pcb to process your existing design file and make edits. (This tool had to read and make edits to the board files, so represented a barrier to format changes. This was probably not the initial motivation of the new mechanism, but represents a big plus point to its existence). Underlying the mechanism is a netlist backend for gnetlist which describes the components and nets of the design using a series of pcb action commands. These are executed by pcb on the open design, and in turn update the internal view of the netlist. The "old" netlist format is not deprecated, although it does not convey all of the information about parts etc.. (gsch2pcb managed that aspect based upon a template file a separate gnetlist backend would populate with all the parts of a given design). Since gsch2pcb and associated netlist backends were in a separate code base to pcb, this represented a compatibility problem if ever we changed things with the file format. The new backend lives with PCB (iirc), so merely relies on gnetlist keeping a stable scheme api and command line interface. You might be interested to know that the update mechanism can be wired to call a makefile (or other scripts?) to generate the required data, so it is infact quite general. Only the "schematics" attributes are really assumed to come from a simple gschem work flow. At some point, I may update xgsch2pcb to use this new mechanism, rather than gsch2pcb. It seems redundant to update gsch2pcb itself though. Peter --089e011603f6f567fa0529263fed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p dir=3D"ltr"><br> On 12 Jan 2016 17:02, "Frank Miles (<a href=3D"mailto:fpm AT u DOT washington= .edu">fpm AT u DOT washington DOT edu</a>) [via <a href=3D"mailto:geda-user AT delorie DOT co= m">geda-user AT delorie DOT com</a>]" <<a href=3D"mailto:geda-user AT delorie= .com">geda-user AT delorie DOT com</a>> wrote:<br> ></p> <p dir=3D"ltr">> Perhaps I'm confused.=C2=A0 I thought I had read th= at the netlist import was<br> > deprecated, and that the proper way of importing the netlist was throu= gh<br> > PCB:File/Import Schematics.=C2=A0 If netlist import is still equally v= alid,<br> > then please accept my apology for the needless noise.<br> ><br> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 -F</p> <p dir=3D"ltr">The import mechanism was added as a more integrated way of r= etrieving this information, rather than relying on an external tool,=C2=A0 = gsch2pcb to process your existing design file and make edits. (This tool ha= d to read and make edits to the board files, so represented a barrier to fo= rmat changes. This was probably not the initial motivation of the new mecha= nism, but represents a big plus point to its existence).</p> <p dir=3D"ltr">Underlying the mechanism is a netlist backend for gnetlist w= hich describes the components and nets of the design using a series of pcb = action commands. These are executed by pcb on the open design, and in turn = update the internal view of the netlist.</p> <p dir=3D"ltr">The "old" netlist format is not deprecated, althou= gh it does not convey all of the information about parts etc.. (gsch2pcb ma= naged that aspect based upon a template file a separate gnetlist backend wo= uld populate with all the parts of a given design).</p> <p dir=3D"ltr">Since gsch2pcb and associated netlist backends were in a sep= arate code base to pcb, this represented a compatibility problem if ever we= changed things with the file format. The new backend lives with PCB (iirc)= , so merely relies on gnetlist keeping a stable scheme api and command line= interface.<br></p> <p dir=3D"ltr">You might be interested to know that the update mechanism ca= n be wired to call a makefile (or other scripts?) to generate the required = data, so it is infact quite general. Only the "schematics" attrib= utes are really assumed to come from a simple gschem work flow.</p> <p dir=3D"ltr">At some point, I may update xgsch2pcb to use this new mechan= ism, rather than gsch2pcb. It seems redundant to update gsch2pcb itself tho= ugh.</p> <p dir=3D"ltr">Peter<br> </p> --089e011603f6f567fa0529263fed--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |