Mail Archives: geda-user/2016/01/13/14:08:37
--089e0122f088cb57a805293bdff4
Content-Type: text/plain; charset=UTF-8
On Wed, Jan 13, 2016 at 5:24 AM, M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> On 12/01/16 17:19, Peter Clifton (petercjclifton AT googlemail DOT com) [via
> geda-user AT delorie DOT com] wrote:
>
>
> 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
>
> I confess to never using the Import Schematics, probably because its only
> just appeared in the builds I have ready access to. I have never had any
> problems with the gsch2pcb workflow, like much of geda-gaf, it's quirky,
> but it works, and and you soon figure out how to make it do what is
> necessary.
>
It took me a long time to get around to trying it as well, for about the
same reason. It's worth it though, especially if you find yourself making
a lot of small changes on the gschem side and routing them incrementally.
Britton
--089e0122f088cb57a805293bdff4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Jan 13, 2016 at 5:24 AM, M. J. Everitt (<a href=3D"mailto:m.j.e=
veritt AT iee DOT org">m DOT j DOT everitt AT iee DOT org</a>) [via <a href=3D"mailto:geda-user AT d=
elorie.com">geda-user AT delorie DOT com</a>] <span dir=3D"ltr"><<a href=3D"mai=
lto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>><=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
=20
=20
=20
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
On 12/01/16 17:19, Peter Clifton (<a href=3D"mailto:petercjclifton AT goog=
lemail.com" target=3D"_blank">petercjclifton AT googlemail DOT com</a>)
[via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-us=
er AT delorie DOT com</a>] wrote:<br>
<blockquote type=3D"cite">
<p dir=3D"ltr"><br>
On 12 Jan 2016 17:02, "Frank Miles (<a href=3D"mailto:fpm AT u DOT wa=
shington.edu" target=3D"_blank">fpm AT u DOT washington DOT edu</a>)
[via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">ged=
a-user AT delorie DOT com</a>]"
<<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda=
-user AT delorie DOT com</a>>
wrote:<br>
></p>
<p dir=3D"ltr">> Perhaps I'm confused.=C2=A0 I thought I had r=
ead that
the netlist import was<br>
> deprecated, and that the proper way of importing the
netlist was through<br>
> PCB:File/Import Schematics.=C2=A0 If netlist import is still
equally valid,<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 retrieving this information, rather than relying on an
external tool,=C2=A0 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).</p>
<p dir=3D"ltr">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.</p>
<p dir=3D"ltr">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).</p>
<p dir=3D"ltr">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.<br>
</p>
<p dir=3D"ltr">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 fr=
om a
simple gschem work flow.</p>
<p dir=3D"ltr">At some point, I may update xgsch2pcb to use this new
mechanism, rather than gsch2pcb. It seems redundant to update
gsch2pcb itself though.</p>
<p dir=3D"ltr">Peter<br>
</p>
</blockquote>
I confess to never using the Import Schematics, probably because its
only just appeared in the builds I have ready access to. I have
never had any problems with the gsch2pcb workflow, like much of
geda-gaf, it's quirky, but it works, and and you soon figure out ho=
w
to make it do what is necessary.<br>
</div>
</blockquote></div><br></div><div class=3D"gmail_extra" style=3D"">It took =
me a long time to get around to trying it as well, for about the same reaso=
n.=C2=A0 It's worth it though, especially if you find yourself making a=
lot of small changes on the gschem side and routing them incrementally.</d=
iv><div class=3D"gmail_extra" style=3D""><br></div><div class=3D"gmail_extr=
a" style=3D"">Britton</div><div class=3D"gmail_extra"><br></div></div>
--089e0122f088cb57a805293bdff4--
- Raw text -