From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "dvhart@linux.intel.com" <dvhart@linux.intel.com>,
Yocto Mailer <yocto@yoctoproject.org>
Subject: Re: In consistancy in the defition of BBFILE_COLLECTIONS in layer.conf
Date: Thu, 26 May 2011 10:49:25 +0100 [thread overview]
Message-ID: <1306403365.27470.99.camel@rex> (raw)
In-Reply-To: <20110526073937.GL3222@jama.jama.net>
On Thu, 2011-05-26 at 09:39 +0200, Martin Jansa wrote:
> Using machine override has one small benefit
>
> when I have meta-nokia layer which has only recipes with
> COMPATIBLE_MACHINE = "nokia900" and I'm building different machine (like
> om-gta02) I get this warning:
> WARNING: No bb files matched BBFILE_PATTERN_nokia-layer '^/OE/shr-core/meta-smartphone/meta-nokia/'
> because all bb files from this layer are ignored because of
> COMPATIBLE_MACHINE
I think there is a change on bitbake master which should fix some of the
cases where this warning was appearing (where a layer only
contained .bbappend files).
> if I change it like this
> -BBFILE_COLLECTIONS += "nokia-layer"
> +BBFILE_COLLECTIONS_nokia900 += "nokia-layer"
> maybe with more overrides per layer.conf if it supports multiple
> machines, the warning is gone, but seems like sstate checksums are
> different again, because during test I changed only this and another gcc
> rebuild is in runqueue now :/.
Ouch. If you can figure out what changed we can try and fix that. FWIW,
I also merged the signature generation data writing at stamp creation
time (with fixes).
Cheers,
Richard
next prev parent reply other threads:[~2011-05-26 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 1:17 In consistancy in the defition of BBFILE_COLLECTIONS in layer.conf Jeremy Puhlman
2011-05-26 3:37 ` Tom Zanussi
2011-05-26 3:49 ` Jeremy Puhlman
2011-05-26 7:39 ` Martin Jansa
2011-05-26 9:49 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-26 0:54 Jeremy Puhlman
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=1306403365.27470.99.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.