From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [PATCH 0/1] linux-yocto: fix externalsrc builds
Date: Tue, 27 Mar 2012 22:31:13 -0400 [thread overview]
Message-ID: <cover.1332901487.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
This is a fix for externalsrc builds when the linux-yocto bbclass
is used.
The commit tells most of the story:
-----
There are a few extra task that modify the source tree that should
be removed when externalsrc is inherited by a recipe that uses a
linux-yocto tree.
Adding those tasks to SRCTREECOVEREDTASKS means that they are skipped
and externalsrc works as intended.
-----
You'll note that do_patch is repeated in SRCTREECOVEREDTASKS here,
since my tested showed that only having it in externalsrc.bbclass
did not inhibit the kernel-yocto.bbclass variant from running
There's no impact if externalsrc isn't being used, so this is a
safe change (from where I stand :)
Cheers,
Bruce
The following changes since commit 7b01671f54f70c28c98457058c51ffefcb07c0e8:
nspr 4.8.9: failed to build on x86_64 board (2012-03-27 13:26:37 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
linux-yocto: support externalsrc builds
meta/classes/kernel-yocto.bbclass | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-03-28 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 2:31 Bruce Ashfield [this message]
2012-03-28 2:31 ` [PATCH 1/1] linux-yocto: support externalsrc builds Bruce Ashfield
2012-03-28 9:12 ` Richard Purdie
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=cover.1332901487.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.com \
/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.