X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-type:content-transfer-encoding;
	bh=uJNxExGrMvABnczz4m6df1pWlUaNeMGBxWvHatISV+Q=;
	b=KiLwSrGfuGBKcj9tNmkKO141EnrtUjjgHBxjpHnGQgiB6F0zZkgpSsgj3D2kdCaBCj
	e0wg0vsMkJ2NM6c+tAqY4Mwffp+uj3oE9SS8iiATNa3HiZb4Jz5zUGX2m4Hu/xH4i9Dw
	x+/L7kv97cro0SD5mv+0EJgke/GMd8jz5WMeSMyjVm+i+Rx6GmvFlbR7g+Fs9pSuYIgs
	lZYOxBen4DFWgd/Zu9s9Rcbsth6tcH4fbuyqCN8ZDW7Q0liHu6t8NbEhS6/Bx9cO5Vws
	wVCvENkgiU6ueyhzFf2sV3ddncNGFfexMK+VGKeXZ4UoB36aXnliwgHdqfPySqo+atRE
	XMCw==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	bh=uJNxExGrMvABnczz4m6df1pWlUaNeMGBxWvHatISV+Q=;
	b=l5jpB9qtbzlmBkhwIU9FID39cDtQXQoJ+T1SEbVjpxWeaRGN1MfzP7b8Gk29/R5K+D
	zYmw+cpOKxwm5eg666rAuv70vO4QXRb0wGHcWh7c9u6g2X1bDDtiAZjd6G660xjO5w+M
	kCsgutCepBb1mYicONxpPmUvBCC9A9zJ2loUy1STWRESb9vXvgCwyklZjp/YMF/VT+vK
	3ScovAgJAUt/hGkfbeOLzs9ZLAtWWQ3JHdL4sNtpsdx97EURKkhI3512YIknU9TDjE92
	2JqYx9hFO2gjFIJuprKolSEkmhrZIkvJ6uBH3Fz8oVH505vjLMmpmoawVEXXTk/JEkjI
	kR+A==
X-Gm-Message-State:	ALoCoQnBE839e9UGg+UWw1mh/1WiZ8a3slLzBz8TEaDCXXSiaTR/CDQsL16AxPUfIxFVTq47GKTPWz4TODk1Sm4EBBxa1mm97g==
X-Received:	by 10.28.13.213 with SMTP id 204mr20217656wmn.16.1452619762037;
	Tue, 12 Jan 2016 09:29:22 -0800 (PST)
Date:	Tue, 12 Jan 2016 18:29:14 +0100
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Re: off-board ... (Import schematics, load
	netlist/layout to buffer)
Message-Id:	<20160112182914.16b80ef9ddc07d782eef22e3@gmail.com>
In-Reply-To:	<alpine.LRH.2.01.1601120839240.16881@homer01.u.washington.edu>
References:	<CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com>
	<8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601040930510 DOT 18447 AT homer02 DOT u DOT washington DOT edu>
	<AF9F11C6-29A4-4558-85C8-973AB80BADFF AT noqsi DOT com>
	<CAC4O8c_ckyybeLDoV9oGM8cdH08goyqw6zG0eFn4dYdG_wchwg AT mail DOT gmail DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601060831110 DOT 31979 AT homer02 DOT u DOT washington DOT edu>
	<29B50AD8-DCD0-4048-B888-711C5D8E1E65 AT noqsi DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601070826250 DOT 1447 AT homer01 DOT u DOT washington DOT edu>
	<20160107175042 DOT 5e06aad2bf09818a8886d6f7 AT gmail DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601080823510 DOT 14656 AT homer03 DOT u DOT washington DOT edu>
	<20160108182822 DOT 3c4b5f2d183143b4a41680dd AT gmail DOT com>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601111041200 DOT 28725 AT homer02 DOT u DOT washington DOT edu>
	<201601111903 DOT u0BJ3A9a005050 AT envy DOT delorie DOT com>
	<5693FF30 DOT 1020208 AT iee DOT org>
	<alpine DOT LRH DOT 2 DOT 01 DOT 1601120839240 DOT 16881 AT homer01 DOT u DOT washington DOT edu>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

> >>> To repeat my previous question: what's so hard about getting pcb to
> >>> understand a circuit from a netlist?  This would allow a variety of
> >>> custom "schematic alterations" that cannot happen if gPCB reads the
> >>> schematic directly.
> >> Since pcb *does* read netlists as part of its normal import, I guess
> >> the answer is "it's not hard".  It imports other information too,
> >> though, like footprint selections.
> >>
> >> It sounds like your problem isn't getting pcb to understand a netlist,
> >> it's getting the tools to emit the right netlist.
> > The pcb NEEDS and USES a netlist .. it's usually appended to the pcb
> > file... what's the issue?!
> 
> 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.

As far as I understand import schematics load both netlist and make sure list of footprints match the schematic?

Load layout and element to buffer probably belong better under the buffer. gsch2pcb or gnetlist may be used to output a file of which layout/footprints need to be added to pcb file and the netlist.

Different input paths is a little bit confusing and some kind of grouping might be useful but I can't figure out anything good.


Nicklas Karlsson

- Raw text -