X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Thu, 7 Dec 2017 14:05:21 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] How to avoid page connector refdes in netlist?
In-Reply-To: <95055344-b5df-b3d2-71c7-ad5148cee46a@ecosensory.com>
Message-ID: <alpine.DEB.2.20.1712071401300.2816@nimbus>
References: <95055344-b5df-b3d2-71c7-ad5148cee46a AT ecosensory DOT com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
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

On Wed, 6 Dec 2017, John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com] 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.

If you use multiple flat schematic pages, gnetlist treats them as if the 
contents of all pages were on one big page.  The backends only see the 
resulting netlist, so it shouldn't make any difference to drc2.