From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC] pkg-kconfig: support alternative .config location
Date: Sun, 11 Sep 2016 20:11:50 +0200 [thread overview]
Message-ID: <20160911181150.GO5740@free.fr> (raw)
In-Reply-To: <20160911200726.7dac0633@itchy>
?ric, All,
On 2016-09-11 20:07 +0200, Eric Le Bihan spake thusly:
> Le Sun, 11 Sep 2016 19:34:03 +0200,
> "Yann E. MORIN" <yann.morin.1998@free.fr> a ?crit :
>
> > On 2016-09-11 19:07 +0200, Eric Le Bihan spake thusly:
> > > Kconfig clones, such as openconf used by xvisor [1], do not look
> > > for .config at the root of the build directory, but in a
> > > subdirectory (e.g. build/openconf).
> > >
> > > This patch introduces a new Makefile variable named
> > > $(2)_KCONFIG_BUILD_FILE, which defaults to $$($(2)_DIR)/.config and
> > > can be overridden in the package Makefile.
> > >
> > > This allows the use of the kconfig-package infrastructure with
> > > packages relying on such clones.
> > >
> > > [1] https://github.com/xvisor/xvisor/tree/master/tools/openconf
> > >
> > > Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr>
> > > ---
> > > package/pkg-kconfig.mk | 14 ++++++++------
> > > 1 file changed, 8 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/package/pkg-kconfig.mk b/package/pkg-kconfig.mk
> > > index b0f5178..82561de 100644
> > > --- a/package/pkg-kconfig.mk
> > > +++ b/package/pkg-kconfig.mk
> > > @@ -36,6 +36,7 @@ $(2)_KCONFIG_EDITORS ?= menuconfig
> > > $(2)_KCONFIG_OPTS ?=
> > > $(2)_KCONFIG_FIXUP_CMDS ?=
> > > $(2)_KCONFIG_FRAGMENT_FILES ?=
> > > +$(2)_KCONFIG_BUILD_FILE ?= $$($(2)_DIR)/.config
> >
> > I think it would be better to name the variable
> > $(2)_KCONFIG_DOTCONFIG_FILE or maybe just $(2)_KCONFIG_DOTCONFIG.
>
> OK.
Before changing the variable name, please a bit ofr others to comment.
> > Otherwise, the rest of the patch is a mere search-and-replace, so
> > looks pretty OK.
> >
> > However, I don't see the point in having that in Buildroot without an
> > actuall package that uses that. Do you plan in sending such a package
> > (like xvisor)?
>
> Yes, I will send a patch to add a xvisor package shortly.
Great! Can you make that a series: this patch followed by the xvisor one?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-09-11 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 17:07 [Buildroot] [PATCH RFC] pkg-kconfig: support alternative .config location Eric Le Bihan
2016-09-11 17:34 ` Yann E. MORIN
2016-09-11 18:07 ` Eric Le Bihan
2016-09-11 18:11 ` Yann E. MORIN [this message]
2016-09-11 21:15 ` Arnout Vandecappelle
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=20160911181150.GO5740@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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