X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Scanned: Debian amavisd-new at gag.com
From: Bdale Garbee <bdale AT gag DOT com>
To: "N \(nicklas.karlsson17\@gmail.com\) \[via geda-user\@delorie.com\]" <geda-user AT delorie DOT com>,
        geda-user AT delorie DOT com
Subject: Re: [geda-user] gnetlist, attributes
In-Reply-To: <20191214230741.98800b1957f2c34454c9d7a6@gmail.com>
References: <20191214172404 DOT 6663931f1c12829227071ee1 AT gmail DOT com> <59B26BA0-D385-4C52-A65C-82AFAE39B470 AT noqsi DOT com> <20191214195933 DOT 71b2dbd5069bc948f48af760 AT gmail DOT com> <CAHUm0tMpSOe4KYp2hLKwqgrCMs1WfaEgf2yXrD3JmskCL+eF1A AT mail DOT gmail DOT com> <20191214230741 DOT 98800b1957f2c34454c9d7a6 AT gmail DOT com>
Date: Sat, 14 Dec 2019 16:38:18 -0700
Message-ID: <87sglmtr4l.fsf@gag.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha512; protocol="application/pgp-signature"
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

"N (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]"
<geda-user AT delorie DOT com> writes:

>> If I am not mistaken, using the
>>=20
>> file -  import schematic
>>=20
>> Functionality is the simplest way to import a netlist.
>
> That's what I used. Then it did not work I investigated and found it call=
 gnetlist or lepton-netlist which is the reason I asked about these.
>
>> http://repo.hu/cgi-bin/pool.cgi?cmd=3Dshow&node=3Dimport_sch
>
> Read this and discovered a new tEDAx format for netlist have already
> been implemented in both lepton and pcb-rnd. This new tEDAx netlist
> file format also have footprint value for the components so that all
> communication in between use this format!

FYI, I wrote the tEDAx export module for lepton-netlist.

Right now, it conveys the bare minimum set of attributes necessary to
lay out boards using pcb-rnd.  I've used it to put several boards into
production with a 'make pcb' target that looks like:

  pcb:    $(SCHEMATICS) Makefile $(CONFIG)
        lepton-netlist -g tEDAx -o $(PROJECT).tdx $(SCHEMATICS)
        echo 'LoadTedaxFrom(netlist, $(PROJECT).tdx); SaveTo(Layout)' | \
                pcb-rnd --gui batch $(PROJECT).lht

I've talked to Tibor about having more control over where new footprints
get placed on the target board when driving a tEDAx import from the
command line like this, but for the moment, note that any new parts are
highly likely to be placed on top of existing circuitry, and you need to
manually remove any parts on the pcb that are no longer needed (by which
I mean have been removed from the schematic).

If you find a reason to want to transfer additional attributes, it
wouldn't be hard to extend the exporter and associated test suite cases.

Bdale

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAl31cmoACgkQtwRxBYML
n6GLQw/9Er8MdTi+g7DPdsXMatybDKXmJK1f4heMwKTml9paHVUM18wBhd0ammUj
Ndj1D63+dQpGvgp2Y4clPAUuxKVRjIaP4yMVjhWXU9Tf+QNEmReTtuauverOTrLy
eVVomg/sNdcXAo6c1Pt8c7B0UmBGsySfHjATpzc98//4VZMXIc0Cy+ZKyJSA6C/i
BmiqmDkQF0Kani8lziDJpPeZnT4ggyEnQEFybZA19itAyWUpU7e3Nh7NXeHf1iYx
08mVaH294m/wu8JKHBAfxhXePC9XyN6hTbLcNLS+qiWbnPXdrQoUyhmZ1iA+TmoV
DpkW0Xjyhrr6LOcp7A8OmZoDdt/UsD2hdhEnvQTf312Ez2wdQY4c6vVV5LgB0s9L
gCdRKbItjNHpgTsiaTlV3CI+hOE3EhIAGztYq4y7Ky9c/YCAWlseTgwqyeo915Iw
iZfgCZbUgQUEuxRAAr58cgMzajJxRw/aBmArHPJ4S989RAAENg9gtXvQo50jQtZJ
829QzZ12dxjAprfYDi+VS0adyFBp0DEudHhAtT9kNSfEHVkKpGkHR4X6IA0dG+4z
wlsIN6Wd3wH24yQF4KTR+dLwwpgvk9ryOgBjqaVGEy21fbwx0F0CITCVG2WI4y6j
TokoNH3qDM0GJG0NDmhKxYFggxe9CVRkWV5NijtxmrnevZuL88g=
=P/KF
-----END PGP SIGNATURE-----
--=-=-=--