From: ChenQi <Qi.Chen@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Patches, Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 1/1] busybox: add config fragments
Date: Tue, 5 Feb 2013 14:42:25 +0800 [thread overview]
Message-ID: <5110A9D1.20208@windriver.com> (raw)
In-Reply-To: <CADkTA4OuDqRE25oNRbFJCyrWpkkj62HpHHNN4qOFocNnrgSY_w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3084 bytes --]
On 02/02/2013 03:08 AM, Bruce Ashfield wrote:
>
>
>
> On Fri, Feb 1, 2013 at 1:56 PM, Saul Wold <sgw@linux.intel.com
> <mailto:sgw@linux.intel.com>> wrote:
>
> On 02/01/2013 06:18 AM, Bruce Ashfield wrote:
>
>
>
>
> On Fri, Feb 1, 2013 at 4:00 AM, <Qi.Chen@windriver.com
> <mailto:Qi.Chen@windriver.com>
> <mailto:Qi.Chen@windriver.com <mailto:Qi.Chen@windriver.com>>>
> wrote:
>
> From: Chen Qi <Qi.Chen@windriver.com
> <mailto:Qi.Chen@windriver.com> <mailto:Qi.Chen@windriver.com
> <mailto:Qi.Chen@windriver.com>>>
>
>
> Add config fragments to busybox.
>
> Both the implementation and the use case are similar to
> yocto kernel's
> configuration fragments.
>
>
> I can fairly easily tweak the configuration parts of the
> kern-tools to
> handle this
> use case as well. That would allow us to re-use the kernel's
> merge_config.sh
> script (with a minor dependency change) and save some
> duplicated code. It
> also gets you the advantage that you can consolidate
> configuration fragments
> outside of any build system, which isn't as critical here, but
> something
> that
> is used quite a bit during kernel testing.
>
> Bruce,
>
> Where is the merge_config.sh script today? Would you propose
> moving it to the scripts dir and have the busybox recipe call it?
>
>
> It's part of the mainline kernel, hence why grabbing the guts out of
> it reproducing
> it here isn't the best idea, we'll have a need to keep them in sync.
> In fact, I have
> 2 or 3 pending patches for it in the kern-tools repository that I need
> to get upstream
> (as an example).
>
> I'd propose either creating a separate recipe for it (i.e. like
> kconfig-frontends) or I could
> keep it in kern-tools (badly named, but we can work on that ;) and
> maintain / coordinate
> changes to it.
>
> I just don't want to see the effort happen twice, we are busy enough!
>
>
> What would be your timing on making such a change, ie hold this
> patch until your get it merge or merge this and then fix it when
> you merge your changes?
>
>
> I could feasibly get it done in the next few weeks, the changes aren't
> bug, I just
> have to avoid regressions on either side (kernel or busy box).
>
> That being said, the interface to the SRC_URI is the same for the two,
> so if we are
> ok with me arriving and removing the in-recipe support, I guess I
> can't object too
> much :) The only risk is that if anyone starts using this first
> support immediately,
> I do risk regressing their use case, where if it never goes in, that
> won't happen.
>
> Cheers,
>
> Bruce
>
>
Hi Bruce,
I just tried to reuse the kernel's merge_config.sh script, and it turned
out well.
The patch is in attachment.
Is it enough for now?
If so, I'll send out the patch.
Thanks,
Chen Qi
[-- Attachment #1.2: Type: text/html, Size: 6518 bytes --]
[-- Attachment #2: 0001-busybox-add-config-fragments.patch --]
[-- Type: text/x-patch, Size: 1511 bytes --]
From a9d36bf24f349f046e9b65ccf4af3352c4dedabf Mon Sep 17 00:00:00 2001
From: Chen Qi <Qi.Chen@windriver.com>
Date: Tue, 5 Feb 2013 14:36:40 +0800
Subject: [PATCH] busybox: add config fragments
Add config fragments to busybox.
The implementation makes use of merge_config.sh script in kern-tools-native.
The use case is similar to the yocto kernel's configuration fragments.
[YOCTO #3379]
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
---
meta/recipes-core/busybox/busybox.inc | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
index 972e7d0..6ed5e09 100644
--- a/meta/recipes-core/busybox/busybox.inc
+++ b/meta/recipes-core/busybox/busybox.inc
@@ -37,6 +37,8 @@ RRECOMMENDS_${PN} = "${PN}-syslog ${PN}-udhcpc"
inherit cml1 update-rc.d
+do_config[depends] = "kern-tools-native:do_populate_sysroot"
+
# internal helper
def busybox_cfg(feature, features, tokens, cnf, rem):
if type(tokens) == type(""):
@@ -112,8 +114,19 @@ do_prepare_config () {
fi
}
+# returns all the elements from the src uri that are .cfg files
+def find_cfgs(d):
+ sources=src_patches(d, True)
+ sources_list=[]
+ for s in sources:
+ if s.endswith('.cfg'):
+ sources_list.append(s)
+
+ return sources_list
+
do_configure () {
do_prepare_config
+ merge_config.sh -m .config ${@" ".join(find_cfgs(d))}
cml1_do_configure
}
--
1.7.9.5
next prev parent reply other threads:[~2013-02-05 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 9:00 [PATCH 0/1] busybox: add config fragments Qi.Chen
2013-02-01 9:00 ` [PATCH 1/1] " Qi.Chen
2013-02-01 14:18 ` Bruce Ashfield
2013-02-01 18:56 ` Saul Wold
2013-02-01 19:08 ` Bruce Ashfield
2013-02-05 3:01 ` ChenQi
2013-02-05 6:42 ` ChenQi [this message]
2013-02-05 16:29 ` Bruce Ashfield
2013-02-12 13:21 ` Richard Purdie
2013-02-12 14:06 ` Bruce Ashfield
2013-02-12 15:32 ` Richard Purdie
2013-02-12 16:50 ` Bruce Ashfield
2013-02-13 16:53 ` Richard Purdie
2013-02-13 16:59 ` Bruce Ashfield
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=5110A9D1.20208@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=bruce.ashfield@gmail.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