public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Barker <pbarker@konsulko.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 5/5] kernel-yocto.bbclass: Support config fragments with externalsrc
Date: Mon,  9 Mar 2020 14:21:39 +0000	[thread overview]
Message-ID: <20200309142139.15741-6-pbarker@konsulko.com> (raw)
In-Reply-To: <20200309142139.15741-1-pbarker@konsulko.com>

The merging of config fragments is performend in the do_kernel_configme
task and so config fragments will not be supported when this task is
removed from the dependency tree.

kernel-yocto adds additional tasks which may modify the source directory
to SRCTREECOVEREDTASKS so that they are removed when using externalsrc.
However, do_kernel_configme should be safe to use, the only modification
to the source tree is the potential creation of the '.kernel-meta'
directory and the '.metadir' file.

Signed-off-by: Paul Barker <pbarker@konsulko.com>
---
 meta/classes/kernel-yocto.bbclass | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index d71ce212a8..6792c9a233 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -1,5 +1,5 @@
 # remove tasks that modify the source tree in case externalsrc is inherited
-SRCTREECOVEREDTASKS += "do_kernel_configme do_validate_branches do_kernel_configcheck do_kernel_checkout do_fetch do_unpack do_patch"
+SRCTREECOVEREDTASKS += "do_validate_branches do_kernel_configcheck do_kernel_checkout do_fetch do_unpack do_patch"
 PATCH_GIT_USER_EMAIL ?= "kernel-yocto@oe"
 PATCH_GIT_USER_NAME ?= "OpenEmbedded"
 
@@ -325,6 +325,7 @@ do_validate_branches[depends] = "kern-tools-native:do_populate_sysroot"
 do_kernel_configme[depends] += "virtual/${TARGET_PREFIX}binutils:do_populate_sysroot"
 do_kernel_configme[depends] += "virtual/${TARGET_PREFIX}gcc:do_populate_sysroot"
 do_kernel_configme[depends] += "bc-native:do_populate_sysroot bison-native:do_populate_sysroot"
+do_kernel_configme[depends] += "kern-tools-native:do_populate_sysroot"
 do_kernel_configme[dirs] += "${S} ${B}"
 do_kernel_configme() {
 	# translate the kconfig_mode into something that merge_config.sh
-- 
2.20.1



      parent reply	other threads:[~2020-03-09 14:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-09 14:21 [PATCH 0/5] Archiver and externalsrc fixes Paul Barker
2020-03-09 14:21 ` [PATCH 1/5] archiver.bbclass: Handle gitsm URLs in the mirror archiver Paul Barker
2020-03-10 23:16   ` Richard Purdie
2020-03-11 11:31     ` Paul Barker
2020-03-11 11:38       ` Richard Purdie
2020-03-11 11:50         ` Paul Barker
2020-03-11 11:53           ` Richard Purdie
2020-03-09 14:21 ` [PATCH 2/5] archiver.bbclass: Make do_deploy_archives a recursive dependency Paul Barker
2020-03-10 23:18   ` Richard Purdie
2020-03-11 11:40     ` Paul Barker
2020-04-01 14:49       ` [OE-core] " Mark Hatle
     [not found]       ` <1601B99892621331.16702@lists.openembedded.org>
2020-04-01 17:20         ` Mark Hatle
2020-03-09 14:21 ` [PATCH 3/5] kernelsrc.bbclass: Fix externalsrc support Paul Barker
2020-03-09 14:21 ` [PATCH 4/5] perf: " Paul Barker
2020-03-09 14:21 ` Paul Barker [this message]

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=20200309142139.15741-6-pbarker@konsulko.com \
    --to=pbarker@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox