Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id C13E6E014F2 for ; Sat, 20 Apr 2013 06:37:29 -0700 (PDT) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 20 Apr 2013 06:37:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,513,1363158000"; d="scan'208";a="325412159" Received: from unknown (HELO [10.255.13.221]) ([10.255.13.221]) by fmsmga002.fm.intel.com with ESMTP; 20 Apr 2013 06:37:28 -0700 Message-ID: <1366465052.27207.74.camel@empanada> From: Tom Zanussi To: "Robert P. J. Day" Date: Sat, 20 Apr 2013 08:37:32 -0500 In-Reply-To: References: <1366409274.27207.69.camel@empanada> X-Mailer: Evolution 3.4.1 (3.4.1-2.fc17) Mime-Version: 1.0 Cc: Yocto discussion list Subject: Re: clarification about BSP layer names and bblayers.conf file? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Apr 2013 13:37:30 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Sat, 2013-04-20 at 05:35 -0400, Robert P. J. Day wrote: > On Fri, 19 Apr 2013, Tom Zanussi wrote: > > > On Fri, 2013-04-19 at 08:37 -0400, Robert P. J. Day wrote: > > > > > second, the BBLAYERS example there seems overly complicated and > > > potentially confusing to beginners. the fact that meta-yocto is listed > > > as NON_REMOVABLE might make readers wonder how they're supposed to > > > know that. why not go with something a lot more people will see, like, > > > say: > > > > > > BBLAYERS = ?" \ <-- and that looks like a typo > > > /usr/local/src/yocto/meta \ > > > /usr/local/src/yocto/meta-ti \ > > > " > > > > > > BBLAYERS_NON_REMOVABLE ?= " \ > > > /usr/local/src/yocto/meta \ > > > " > > > > > > > I agree - the whole NON_REMOVABLE thing doesn't add anything and should > > be removed - the example is just trying to show how to add a BSP layer - > > the rest just adds potential confusion. And, yeah, it's a typo.. > > i'll let someone else decide what to do there. > > > > finally, the passing reference to layers that contain sub-BSP-layers > > > is good, but show an example, such as the fact that the meta-crownbay > > > layer.conf file has a dependency on meta-intel: > > > > > > ... > > > LAYERDEPENDS_crownbay = "intel" > > > > > > never pass up the opportunity to reinforce an idea with a few lines > > > of actual code. :-) > > > > > > > Agreed, but on the other hand we don't really want to be too > > intel-specific (I know, we have crownbay everywhere else, but anyway..) > > i was just looking for an example of the kind of hierarchical layer > structure you find in meta-intel. is there another layer that has that > kind of structure? > A quick scan of all the layers I have opengrokked here doesn't show any either, so possibly meta-intel is currently the only example. If so, let's use it.. Tom > rday >