From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/5] kernel.bbclass: copy .config instead of moving
Date: Fri, 18 Dec 2015 10:39:42 +0200 [thread overview]
Message-ID: <1450427985-12504-3-git-send-email-markus.lehtonen@linux.intel.com> (raw)
In-Reply-To: <1450427985-12504-1-git-send-email-markus.lehtonen@linux.intel.com>
Copy kernel .config from ${S} to ${B}, instead of moving it. This
prevents mangling the source tree, which is undesirable e.g. when
externalsrc is used.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
---
meta/classes/kernel.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 4ce1611..7de9f20 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -338,7 +338,7 @@ kernel_do_configure() {
touch ${B}/.scmversion ${S}/.scmversion
if [ "${S}" != "${B}" ] && [ -f "${S}/.config" ] && [ ! -f "${B}/.config" ]; then
- mv "${S}/.config" "${B}/.config"
+ cp "${S}/.config" "${B}/.config"
fi
# Copy defconfig to .config if .config does not exist. This allows
--
2.1.4
next prev parent reply other threads:[~2015-12-18 8:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 8:39 [PATCH 0/5] devtool: create kernel config fragment Markus Lehtonen
2015-12-18 8:39 ` [PATCH 1/5] devtool: extract: use the correct datastore for builddir Markus Lehtonen
2015-12-18 8:39 ` Markus Lehtonen [this message]
2015-12-18 12:22 ` [PATCH 2/5] kernel.bbclass: copy .config instead of moving Richard Purdie
2015-12-18 12:39 ` Markus Lehtonen
2015-12-18 14:18 ` Richard Purdie
2015-12-18 15:48 ` Markus Lehtonen
2015-12-18 8:39 ` [PATCH 3/5] devtool: extract: cleanup srctree Markus Lehtonen
2015-12-18 8:39 ` [PATCH 4/5] cml1.bbclass: copy .config to S if externalsr is in use Markus Lehtonen
2015-12-18 8:39 ` [PATCH 5/5] devtool: update-recipe: create kernel config fragment Markus Lehtonen
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=1450427985-12504-3-git-send-email-markus.lehtonen@linux.intel.com \
--to=markus.lehtonen@linux.intel.com \
--cc=openembedded-core@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 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.