From: Stefan Roese <stefan.roese@gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>, yocto@yoctoproject.org
Subject: Re: Board specific bbappend file
Date: Thu, 05 Dec 2013 17:44:34 +0100 [thread overview]
Message-ID: <52A0AD72.5080908@gmail.com> (raw)
In-Reply-To: <52A0AAF6.2000509@windriver.com>
On 05.12.2013 17:33, Bruce Ashfield wrote:
>>> 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"
Yes, right. But this would mean doing it in a "generic" bbappend file? E.g.
recipe:
linux-xyz_3.12.bb
and its "generic" append file:
linux-xyz_3.12.bbappend
And thinking about for example 20 boards, this would mean to add 20
"SRC_URI_fooabc" defines to this bbappend file. Just shifting the
changes from the bb file to the "common" bbappend file.
What I was looking for is more a way to do this on a one-file-per-board
basis. Is this possible somehow?
Thanks,
Stefan
next prev parent reply other threads:[~2013-12-05 16:44 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
2013-12-05 16:44 ` Stefan Roese [this message]
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=52A0AD72.5080908@gmail.com \
--to=stefan.roese@gmail.com \
--cc=bruce.ashfield@windriver.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.