<div dir="ltr">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.</div><br><div class="gmail_quote"><div dir="ltr">On Wed, Feb 24, 2016 at 3:00 PM Robert P. J. Day <<a href="mailto:rpjday@crashcourse.ca">rpjday@crashcourse.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> let's see if i can explain this properly -- i want to enumerate all<br>
possible ways to .bbappend to a kernel recipe if i have multiple<br>
target machines and multiple kernel recipes. so let's imagine the<br>
following scenario -- i grab a layer that has two recipe files for<br>
two versions of the kernel, *and* i have two target boards. so ...<br>
<br>
* <a href="http://linux-4.0.bb" rel="noreferrer" target="_blank">linux-4.0.bb</a><br>
* <a href="http://linux-4.1.bb" rel="noreferrer" target="_blank">linux-4.1.bb</a><br>
<br>
and i have two target machines, "mach1" and "mach2", and the combination<br>
of all of these involves various patches. so what are my possibilities?<br>
<br>
first (as long as i understood chris larson properly), i can define<br>
two separate .bbappend files:<br>
<br>
* linux-4.0.bbappend<br>
* linux-4.1.bbappend<br>
<br>
or i can define a single wildcard .bbappend file that covers both:<br>
<br>
* linux-4.%.bbappend<br>
<br>
so far, so good.<br>
<br>
next, in these .bbappend files, SRC_URI can refer to any of:<br>
<br>
* .scc files<br>
* .patch/.diff files<br>
* .cfg files<br>
<br>
so each of my two .bbappend files can enumerate a different set<br>
of files to be applied to that version of the kernel. but wait ...<br>
there's more.<br>
<br>
in each .bbappend file, i can conditionally include files in the<br>
SRC_URI, as in:<br>
<br>
* SRC_URI_mach1 += mach1.patch<br>
<br>
so depending on the target machine, i can conditionally include<br>
any of patch files, cfg files or scc files.<br>
<br>
in addition, i can take advantage of FILESEXTRAPATHS, that i once<br>
wrote up here:<br>
<br>
<a href="http://www.crashcourse.ca/wiki/index.php/Poky_bbappend_FILESEXTRAPATHS" rel="noreferrer" target="_blank">http://www.crashcourse.ca/wiki/index.php/Poky_bbappend_FILESEXTRAPATHS</a><br>
<br>
so that i have a ridiculous set of possibilities as to which patch<br>
files will be applied depending on the:<br>
<br>
* architecture<br>
* distro<br>
* target machine<br>
<br>
am i making sense so far? because there will be more coming shortly.<br>
<br>
rday<br>
<br>
<br>
<br>
--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div>