From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga02.intel.com ([134.134.136.20]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QPNNs-0006vr-Hi for openembedded-core@lists.openembedded.org; Thu, 26 May 2011 01:21:00 +0200 Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 25 May 2011 16:17:56 -0700 X-ExtLoop1: 1 Received: from unknown (HELO [10.255.12.181]) ([10.255.12.181]) by orsmga002.jf.intel.com with ESMTP; 25 May 2011 16:17:56 -0700 Message-ID: <4DDD8E2C.6010104@linux.intel.com> Date: Wed, 25 May 2011 16:18:04 -0700 From: Darren Hart User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Patches and discussions about the oe-core layer References: <4DDBDE9D.5000709@linux.intel.com> <20110524172330.GC18086@sakrah.homelinux.org> <6D7346D0-2F4B-44EC-A04B-2F443B33E544@dominion.thruhere.net> <1306260430.2491.2.camel@elmorro> <1306333690.2491.82.camel@elmorro> <1306334330.2525.236.camel@phil-desktop> <4DDD50D3.4090202@linux.intel.com> <1306350664.3120.28.camel@lenovo.internal.reciva.com> <4DDD60E3.606@linux.intel.com> <1306359076.27470.65.camel@rex> In-Reply-To: <1306359076.27470.65.camel@rex> Subject: Re: adding meta-intel layers breaks parsing, was Re: Updating u-boot for oe-core or meta-yocto X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2011 23:21:00 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 05/25/2011 02:31 PM, Richard Purdie wrote: > On Wed, 2011-05-25 at 13:04 -0700, Darren Hart wrote: >> >> On 05/25/2011 12:11 PM, Phil Blundell wrote: >>> On Wed, 2011-05-25 at 11:56 -0700, Darren Hart wrote: >>>> If it is indeed space separated then I should be able to remedy both >>>> issues by simply using the append operator and not self-referencing. >>>> Correct? >>> >>> I think that's true, yes. But, space separation is fairly undesirable >>> for anything involving paths (particularly absolute ones) and it is >>> tempting to say that we should change that variable to have a different >>> separator. >>> >> >> The only example I see of concatenating this variable is a prepend which >> uses colons. RP also mentioned he was pretty sure it should be colons. >> I'll figure it out for certain and fix the path assignments in meta-intel. > > I checked the code and it is currently setup to use spaces but all the > users I've seen use colons. > > There is significant precedent for *PATH* variables (FILESPATH, BBPATH, > PATH) being colon delimited so I'm tempted to say the utils.bbclass code > handling this should be fixed for EXTRAFILESPATH. > > Also, the self referencing of that variable is correct. What is missing > is a default value for it, again that needs fixing in the core... I've sent a patch that I believe works. http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/003145.html -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel