From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: require statement does not honor .bbappend
Date: Fri, 03 Feb 2012 15:01:15 +0000 [thread overview]
Message-ID: <1328281275.3895.117.camel@ted> (raw)
In-Reply-To: <4F2BE0D7.7040101@mlbassoc.com>
On Fri, 2012-02-03 at 06:27 -0700, Gary Thomas wrote:
> On 2012-02-03 03:07, Richard Purdie wrote:
> > On Thu, 2012-02-02 at 16:22 -0700, Gary Thomas wrote:
> >> This is really a bitbake problem, but I'll bring it up here.
> >>
> >> I have a statement like this in one of my recipes:
> >> require xyz.bb
> >>
> >> If I also have within my layers a xyz.bbappend file, it gets
> >> processed when I build xyz, e.g.
> >> % bitbake xyz
> >> but is ignored when I only 'require' that recipe.
> >>
> >> Should it not be always processed?
> >
> > No, as designed and implemented you can't bbappend to anything being
> > used as an include (or require), only the final .bb file.
>
> Bummer. What's the rationale behind this [restriction]?
Trying to implement generic "append" files to conf and inc files was
going to be a significant headache for the parser and cache logic,
create a pile of ordering issues and was going to mean significant code
changes. The bbappend files were simple to understand and easy to
implement by comparison.
At the time, bbappend was seen as a sideline feature by most so we went
for the less invasive and simpler implementation (which was simpler to
use too).
Cheers,
Richard
prev parent reply other threads:[~2012-02-03 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 23:22 require statement does not honor .bbappend Gary Thomas
2012-02-03 10:07 ` Richard Purdie
2012-02-03 13:27 ` Gary Thomas
2012-02-03 15:01 ` Richard Purdie [this message]
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=1328281275.3895.117.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=poky@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.