Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: adding meta-intel layers breaks parsing, was Re: Updating u-boot for oe-core or meta-yocto
Date: Wed, 25 May 2011 11:56:19 -0700	[thread overview]
Message-ID: <4DDD50D3.4090202@linux.intel.com> (raw)
In-Reply-To: <1306334330.2525.236.camel@phil-desktop>



On 05/25/2011 07:38 AM, Phil Blundell wrote:
> On Wed, 2011-05-25 at 09:28 -0500, Tom Zanussi wrote:
>> I just finished building all of the above successfully using the latest
>> (as of yesterday) poky/master and meta-intel/master.
>>
>> Not sure why you're seeing parsing errors, none here...
> 
> The way meta-intel is using FILESEXTRAPATHS does look a bit dubious to
> me.  Your kernel .bbappend files seem to be doing:
> 
> FILESEXTRAPATHS := "${FILESEXTRAPATHS}:${THISDIR}/${PN}"
> 
> which seems wrong for two reasons: firstly it will lose if
> FILESEXTRAPATHS wasn't previously set (in which case you'll get a
> circular reference within the value, since bitbake won't expand that
> part of the rvalue during the assignment);

So the reason I had made this change was to allow for multiple layers to
aggregate their bbappends. As it was previously, the meta-intel layer
prevented other layers from working by clobbering the FILESEXTRAPATHS
rather than appending to it.

> and secondly, as far as I can
> tell from looking at utils.bbclass, FILESEXTRAPATHS isn't actually
> supposed to be colon separated in the first place.

Doh. My original patch was space separated and someone suggested colons
and I didn't see a build failure in my testing so I left it. Bad testing
methodology apparently.

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?

> 
> (Also, as a tangential matter, this FILESEXTRAPATHS setting isn't going
> to be producing any useful effect since none of the meta-intel layers
> actually have any files in their recipes-kernel/linux directory.)

We do want it in place so these can be easily added for development
purposes, even though the ultimate goal would be to include such changes
in the kernel source repository.

> 
> p.
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



  parent reply	other threads:[~2011-05-25 18:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 16:36 Updating u-boot for oe-core or meta-yocto Darren Hart
2011-05-24 17:13 ` Koen Kooi
2011-05-24 18:04   ` Darren Hart
2011-05-24 17:23 ` Khem Raj
2011-05-24 17:51   ` adding meta-intel layers breaks parsing, was " Koen Kooi
2011-05-24 18:07     ` Tom Zanussi
2011-05-25 14:28       ` Tom Zanussi
2011-05-25 14:31         ` Koen Kooi
2011-05-25 14:38         ` Phil Blundell
2011-05-25 14:52           ` Tom Zanussi
2011-05-25 18:56           ` Darren Hart [this message]
2011-05-25 19:11             ` Phil Blundell
2011-05-25 20:04               ` Darren Hart
2011-05-25 21:31                 ` Richard Purdie
2011-05-25 23:18                   ` Darren Hart
2011-05-24 18:23   ` Darren Hart
2011-05-24 18:35     ` Khem Raj
2011-05-24 18:48       ` Phil Blundell
2011-05-24 19:33       ` Darren Hart
2011-05-24 17:33 ` Martin Jansa
2011-05-25 15:51 ` Richard Purdie
2011-05-25 16:36   ` Khem Raj
2011-05-25 16:49     ` Henning Heinold
2011-05-25 18:40       ` Darren Hart
2011-05-26  6:12         ` Anders Darander
2011-05-26 13:54           ` Darren Hart
2011-05-25 21:51     ` Richard Purdie
2011-05-25 23:31       ` Jason Kridner
2011-05-26 18:07         ` Darren Hart
2011-05-27  5:36           ` Anders Darander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DDD50D3.4090202@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox