[oe] [Bitbake-dev] A new bitbake extension: .bbappend files

[Chris Larson]

It basically solves the same problem.  It's slightly less flexible, in that
it has to apply to a specific .bb, whereas an amend.inc can apply to any
version of a recipe, etc, depending on where it resides in the FILESPATH,
but amend.inc cannot be integrated into bitbake without a performance
impact, because we don't necessarily know the FILESPATH until after the
finalizing steps at the end of the parsing process, and then it has to
re-finalize after the amend.inc is parsed, to ensure its anonymous python
functions are executed.  The advantage to this is its simplicity in
implementation and the miniscule performance impact.  One slight concern is
its assumption that the basename of the filename is unique, but I expect
that's okay in most real world cases.

I hope to spend some time poking at this today.

-Chris

On Fri, Jul 16, 2010 at 8:46 AM, Michael Smith <msmith at cbnco.com> wrote:

> Hi Richard,
>
> Does this do anything different than amendrecipes.bbclass?
>
> Mike
>
>
> Richard Purdie wrote:
>
>> The idea is that if bitbake finds any X.bbappend files, when it loads
>> X.bb, it will also include these files after it parses the base .bb file
>> (but before finalise and the anonymous methods run). This means that
>> the .bbappend file can poke around and do whatever it might want to the
>> recipe to customise it.
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics