All of lore.kernel.org
 help / color / mirror / Atom feed
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:09:04 -0500	[thread overview]
Message-ID: <52A0A520.7060103@windriver.com> (raw)
In-Reply-To: <52A0A38E.7020903@gmail.com>

On 13-12-05 11:02 AM, Stefan Roese wrote:
> Dear List!
>
> 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.

Bruce

>
> Thanks,
> Stefan
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



  reply	other threads:[~2013-12-05 16:09 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 [this message]
2013-12-05 16:27   ` Stefan Roese
2013-12-05 16:33     ` Bruce Ashfield
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=52A0A520.7060103@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.