Re: [OE-core] trying to summarize the flexibility in bbappend'ing to kernel recipes

2016-02-25 Thread Robert P. J. Day
Quoting "Robert P. J. Day" : (i'm going to reply to this post just to keep everything in the same thread.) ... big snip ... in addition to all of that possible bbappend customization in my earlier note, i just noticed i forgot to mention this possibility of conditional prepending to FILE

Re: [OE-core] trying to summarize the flexibility in bbappend'ing to kernel recipes

2016-02-25 Thread Robert P. J. Day
(i'm going to reply to this post just to keep everything in the same thread.) i'm going to try to clarify all of the ways one can bbappend to a kernel recipe, and i'll have a few questions along the way. as before, let's assume i have access to a layer that already gives me two base recipes

Re: [OE-core] trying to summarize the flexibility in bbappend'ing to kernel recipes

2016-02-24 Thread Christopher Larson
A bbappend basically concatenates to the recipe in bitgbake, so it can do anything the recipe can do, within reason, so yes, use of filespath and overrides works the way it's always worked with recipes. On Wed, Feb 24, 2016 at 3:00 PM Robert P. J. Day wrote: >let's see if i can explain this

[OE-core] trying to summarize the flexibility in bbappend'ing to kernel recipes

2016-02-24 Thread Robert P. J. Day
let's see if i can explain this properly -- i want to enumerate all possible ways to .bbappend to a kernel recipe if i have multiple target machines and multiple kernel recipes. so let's imagine the following scenario -- i grab a layer that has two recipe files for two versions of the kernel, *a