From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: how to apply bbappend selectively
Date: Thu, 28 Jul 2011 11:31:58 +0100 [thread overview]
Message-ID: <201107281131.58174.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4E31324C.3030901@nedap.com>
On Thursday 28 July 2011 10:56:28 Jaap de Jong wrote:
> I.m creating a special image with for instance a modified udev package.
> I've created a udev-xxx.bbappend for that purpose.
> But for all the other images I build for other hardware I still want to
> use the original udev-xxx.
Usually this is just done with machine overrides within the bbappend.
e.g.
SRC_URI_append_somemachine = "file://somefile.patch"
SOMEVARIABLE_somemachine = "value1"
ANOTHERVARIABLE_somemachine = "value2"
That way building for all other machines will be unaffected.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-07-28 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 9:56 how to apply bbappend selectively Jaap de Jong
2011-07-28 10:31 ` Paul Eggleton [this message]
[not found] ` <4E314453.8080107@nedap.com>
2011-07-28 11:17 ` Paul Eggleton
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=201107281131.58174.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox