[yocto] Board specific bbappend file

[Bruce Ashfield]

On 13-12-05 11:27 AM, Stefan Roese wrote:
> Hi Bruce,
>
> On 05.12.2013 17:09, Bruce Ashfield wrote:
>>> I'm trying to add a board specific *.bbappend file to a recipe. To add
>>> board specific informations/settings to this recipe but without changing
>>> the common (generic) recipe (*.bb) file. Something like this:
>>>
>>> recipe:
>>> linux-xyz_3.12.bb
>>>
>>> board-specific append file:
>>> linux-xyz-board-foo_3.12.bbappend
>>>
>>>   From the documentation I read:
>>> "
>>> Append files must have the same root names as their corresponding
>>> recipes. For example, the append file someapp_1.5.1.bbappend must apply
>>> to someapp_1.5.1.bb.
>>> "
>>>
>>> So it seems impossible to "encrypt" the board name into the bbappend
>>> file name. Or am I missing something?
>>>
>>> If not, is there another way to add such board-specific stuff to a
>>> recipe without changing the generic recipe?
>>
>> What exactly are you tried to change on a per-board basis ? Assuming
>> it is variables, you can use the standard OVERRIDES mechanism to
>> have a version specific bbappend, that changes variables on a per
>> board basis.
>>
>> i.e.
>>
>>        FOO_<machine name> = "bar"
>>        FOO_<another machine name> = "bar2"
>>
>> Assuming the generic recipe uses these variables appropriately, you'll
>> be fine.
>
> Specifically its the SRC_URI / SRC_URI_append variable (e.g. for a linux
> kernel and u-boot etc). And since this one is used in many recipes, I
> can't just put those settings in the machine conf file.
>
> Do you have any recommendations how to change this variable (per recipe)
> without touching the generic bb file?

You can absolutely change the SRC_URI on a per-board basis. Just use
the technique that I showed above, and do it in a bbappend to your
linux recipe.

i.e. something like: SRC_URI_qemux86 += "file://myfancypatch.patch"

Cheers,

Bruce

>
> Thanks,
> Stefan
>