From: "Hart, Darren" <darren.hart@intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>,
"Openembedded-core@lists.openembedded.org"
<Openembedded-core@lists.openembedded.org>,
"Ashfield, Bruce (Wind River)" <bruce.ashfield@windriver.com>,
"richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH 1/1] meta-skeleton: linux-yocto-custom.bb: use machine overrides
Date: Fri, 11 Apr 2014 17:18:57 +0000 [thread overview]
Message-ID: <CF6D724D.830D1%darren.hart@intel.com> (raw)
In-Reply-To: <f1c400fe717177e267c91a497143bc0267b5fe17.1397235602.git.nitin.a.kamble@intel.com>
On 4/11/14, 10:05, "Kamble, Nitin A" <nitin.a.kamble@intel.com> wrote:
>From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
>Use machine overrides for variables for this skeleton recipe so that
>people following skeleton do it right at the beginning.
>
>The machine overrides for the variables reduces pollution of name space
>and avoid unintentional influences on other layers.
>
>Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
>---
> meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
>diff --git a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
>b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
>index c329106..76457ca 100644
>--- a/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
>+++ b/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
>@@ -46,10 +46,10 @@ require recipes-kernel/linux/linux-yocto.inc
>
> # Override SRC_URI in a bbappend file to point at a different source
> # tree if you do not want to build from Linus' tree.
>-SRC_URI =
>"git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;protocol
>=git;nocheckout=1;name=machine"
>+SRC_URI_machine =
>"git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;protocol
>=git;nocheckout=1;name=machine"
>
>-LINUX_VERSION ?= "3.4"
>-LINUX_VERSION_EXTENSION ?= "-custom"
>+LINUX_VERSION_machine ?= "3.4"
>+LINUX_VERSION_EXTENSION_machine ?= "-custom"
>
> # Override SRCREV to point to a different commit in a bbappend file to
> # build a different release of the Linux kernel.
>@@ -61,4 +61,4 @@ PV = "${LINUX_VERSION}+git${SRCPV}"
>
> # Override COMPATIBLE_MACHINE to include your machine in a bbappend
> # file. Leaving it empty here ensures an early explicit build failure.
>-COMPATIBLE_MACHINE = "(^$)"
>+COMPATIBLE_MACHINE_machine = "(^$)"
Might as well change this to:
COMPATIBLE_MACHINE_machine = "machine"
And then add a comment at the top to remind people to replace "machine"
with their BSP name.
--
Darren Hart Open Source Technology Center
darren.hart@intel.com Intel Corporation
next prev parent reply other threads:[~2014-04-11 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 17:05 [PATCH 0/1] A kernel recipe fix for meta-skeleton layer nitin.a.kamble
2014-04-11 17:05 ` [PATCH 1/1] meta-skeleton: linux-yocto-custom.bb: use machine overrides nitin.a.kamble
2014-04-11 17:18 ` Hart, Darren [this message]
2014-04-11 17:48 ` Bruce Ashfield
2014-04-11 17:53 ` Kamble, Nitin A
2014-04-15 16:54 ` Paul Eggleton
2014-04-15 18:03 ` Hart, Darren
2014-04-15 23:41 ` Paul Eggleton
2014-04-18 16:12 ` Kamble, Nitin A
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=CF6D724D.830D1%darren.hart@intel.com \
--to=darren.hart@intel.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=bruce.ashfield@windriver.com \
--cc=nitin.a.kamble@intel.com \
--cc=richard.purdie@linuxfoundation.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