X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Message-ID: <1382902814.28349.8.camel@pcjc2lap> Subject: Re: [geda-user] Merging ICs and nets with gsch2pcb From: Peter Clifton To: geda-user AT delorie DOT com Date: Sun, 27 Oct 2013 19:40:14 +0000 In-Reply-To: References: <1382900899 DOT 22421 DOT 6 DOT camel AT pcjc2lap> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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 Sun, 2013-10-27 at 23:50 +0430, James Jackson wrote: > > Ease of navigation (read as laziness if you want). The fact that > everything's getting prefixed with the subcircuit refdes on netlisting > makes me think this really isn't the workflow this was designed for. > Probably not, but I have used it this way myself in the past. Looking at the options available for a gnetlistrc file, (See your $PREFIX/share/gEDA/system-gnetlistrc file for good description of the available options), I also see there is: ; hierarchy-netattrib-mangle string ; ; Controls if net created by using the net= attribute are renamed to make ; them uniq when traversing down into the hierarchy. If this is disabled ; then the net= created nets are not changed. This feature is handy to have ; global nets which spawn the entire hierarchy (like power or ground nets). ; Please make sure you know what you are doing. ; (hierarchy-netattrib-mangle "enabled") ;(hierarchy-netattrib-mangle "disabled") Which, if you understand what it is doing, might allow you to make power nets global without affecting all other net-names assigned with the "netname=..." attribute. -- Peter Clifton Clifton Electronics