From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Stefan Roese <stefan.roese@gmail.com>, <yocto@yoctoproject.org>
Subject: Re: Board specific bbappend file
Date: Thu, 5 Dec 2013 11:33:58 -0500 [thread overview]
Message-ID: <52A0AAF6.2000509@windriver.com> (raw)
In-Reply-To: <52A0A974.9080207@gmail.com>
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
>
next prev parent reply other threads:[~2013-12-05 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 16:02 Board specific bbappend file Stefan Roese
2013-12-05 16:09 ` Bruce Ashfield
2013-12-05 16:27 ` Stefan Roese
2013-12-05 16:33 ` Bruce Ashfield [this message]
2013-12-05 16:44 ` Stefan Roese
2013-12-05 16:51 ` Bruce Ashfield
2013-12-05 18:34 ` Martin Jansa
2013-12-05 17:49 ` Paul Eggleton
2013-12-05 17:52 ` Bruce Ashfield
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=52A0AAF6.2000509@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=stefan.roese@gmail.com \
--cc=yocto@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.