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=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=XLWAP6z0+EP3ZEKQCNmBtwsg6X2jk5SRqYVidW4tmKQ=; b=i7bO+2GazSZxztPZ+znWpfeC9mvQQOzl2EaPq+S1/PCQ+kxrnh+PVNT7NsQrNrCc4k K4uibk+R+JdTbq9RGjwWongVCrADEuwt1cW2WCw5ELqBpEPzXPclQXiTvSyfWYRmb1K1 1lUMgCX+MWKxIi9vrjgEHIsk+BL2v2eya5GPl34M3IQ1T/1p7zl4KAG/diL/iJtW8Hh0 qWGNdmbxeeVp3w28vCicnpQlPbRKrJzhAXc71IAobw+GA/0M9wLWGry/oY2EF297P7xH jNOJXqyVFNl+LctPDPb9XGEklPmoAt09LtUVa6HH086cDkKL9ljmVjIx64ikymAJDGAa tzSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=XLWAP6z0+EP3ZEKQCNmBtwsg6X2jk5SRqYVidW4tmKQ=; b=iX4P29nDX8FFnUG4bWOQwgalsxTMjVWDXmGyAWezRNHClGtFLNFA85ogAgU1A4umub Uc8P4x06jp6UriFGE1zz3/1Ma//mQcC4xcH6K7VlCXAGOMrI0fJzqeFH3vndASqb6thT QFEBsAyp8nMoXXCxw19pn4hR04rWQyNS+gheB6UV4q0Fu6qfFRFTRF5u4D81Zof8Cqax xJM5nLW2PJfYWJMfWQ4Dr+BTF7L4CfujoidnGhUZ1cY4NftfB7UbAknpuJsE8FpnXIu1 b4RZ3Y3UjUmQW6LLMUfRqOexLu+N6W10+2m6dCDz5AE4Ozg4VbZVNzLiWmHC4LYAblN3 Jx6A== X-Gm-Message-State: ALyK8tJguAHEhDJw4l8DduikMD/mEWnEUwrCi/I8bSf8uBxHnb2yiXG4dPVU7gVXS/sURMdSCXWHTIk+ZeInLg== MIME-Version: 1.0 X-Received: by 10.37.97.145 with SMTP id v139mr8922105ybb.153.1464473694136; Sat, 28 May 2016 15:14:54 -0700 (PDT) In-Reply-To: References: <20160528103918 DOT 82b3ae3b0e381a5e72b6b4cb AT gmail DOT com> Date: Sun, 29 May 2016 03:44:54 +0530 Message-ID: Subject: Re: [geda-user] Hierarchial schematics, gnetlist, and attribs From: "Shashank Chintalagiri (shashank DOT chintalagiri AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 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 The bom backend also respects the contents of the attribs file - I've successfully been able to extract all manner of attributes using that method. When traversing the hierarchical schematic, though, there doesn't seem to be an obvious way to access the attributes of the 'parent'. I will try to use the hierarchical traversal disabled switch, though I would like to be able to do it on a per-run basis. i.e., I would first get bom.net with the bom backend, and then bom-top.net without hierarchical traversal to get a list of all the sources and associated refdes's of the symbols of subcircuits. Doing though by changing the gafrc file seems inappropriate. The ideal solution, though I'm not quite sure how to implement it, would be if when traversing hierarchical schematics, the 'child' packages inherit all the attributes of the 'parent' - so that any attributes of the parent which the child does not override, will trickle through down the hierarchy tree (however deep it may be) and remain accessible in the final, flattened BOM. On Sat, May 28, 2016 at 5:06 PM, Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] wrote: > I think you may be able to achieve what you want by disabling hierarchy > traversal when processing the BOM. This can be done via a directive in the > gafrc file. > > With hierarchy traversal disabled, "source=.." attributes should (I think) > just be another which can come out in the BOM listing. > > I think you might also want to try the "bom2" back-end, which allows you to > explicitly list what attributes you want to export. > > > Peter -- Chintalagiri Shashank Indian Institute of Technology, Kanpur http://blog.chintal.in