X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] How to avoid page connector refdes in netlist?
To:	geda-user AT delorie DOT com
References:	<95055344-b5df-b3d2-71c7-ad5148cee46a AT ecosensory DOT com>
	<alpine DOT DEB DOT 2 DOT 20 DOT 1712071401300 DOT 2816 AT nimbus>
From:	"John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<be6963d6-ff7f-c051-6182-080700e6be48@ecosensory.com>
Date:	Thu, 7 Dec 2017 09:52:45 -0600
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
	Thunderbird/52.4.0
MIME-Version:	1.0
In-Reply-To:	<alpine.DEB.2.20.1712071401300.2816@nimbus>
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

On 12/07/2017 07:05 AM, Roland Lutz wrote:
>> I was wanting to use 2 flat gschem schematic pages with connectors for making a netlist, but found that drc2 flagged net only 
>> connected to one pin when using no refdes, and refdes included in netlist when using one.
>>
>> Should we just ignore the drc2 error?
> 
> I'm afraid I don't understand your question.

Well, it's about using a page connector to have a multi page flat schematic.  I've never really found a way that does not
generate a drc error.  Is there a way?  For me, it's moot now -- worked around it.


What I usually do, (and also did this time), is to use the gschem hierarchic-flat netlist that inserts subcircuit
refdes's into the flat netlist to give you net nodes such as S1/R33-2.  With that style, gnetlist follows the source= attributes 
to subcircuit schematics and my makefile works easily to process drc's netlists for any that are updated.

Multi page flat schematics would be some difficult makefile writing also, so dropping the "page connector to have a multi page 
flat schematic" request/question.

- Raw text -