From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5 v4] busybox: convert to kconfig-package infrastructure
Date: Mon, 4 Aug 2014 10:01:15 +0200 [thread overview]
Message-ID: <20140804100115.6739393e@free-electrons.com> (raw)
In-Reply-To: <437a2f63b7dd1357bf859133053f4b877bc2a0e9.1407079864.git.yann.morin.1998@free.fr>
Yann, Thomas,
On Sun, 3 Aug 2014 17:32:43 +0200, Yann E. MORIN wrote:
> +BUSYBOX_KCONFIG_FILE = $(BUSYBOX_CONFIG_FILE)
> +BUSYBOX_KCONFIG_EDITORS = menuconfig xconfig gconfig
> +BUSYBOX_KCONFIG_OPT = $(BUSYBOX_MAKE_OPTS)
At some point, maybe we'll want to refactor this a bit. It seems silly
to define BUSYBOX_CONFIG_FILE and BUSYBOX_MAKE_OPTS to then have to
"rename" them just for the sake of the kconfig-package infra usage. Why
not giving them the right name for the beginning?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-08-04 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 15:32 [Buildroot] [PATCH 0/5 v4] Introduction of kconfig-package (branch yem/patrickdp/kconfig-pkg) Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 1/5 v4] uclibc: fixup config before calling menuconfig Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 2/5 v4] infra: introduce a kconfig-package infrastructure Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 3/5 v4] manual: add documentation for kconfig-package Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 4/5 v4] uclibc: convert to kconfig-package infrastructure Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 5/5 v4] busybox: " Yann E. MORIN
2014-08-04 8:01 ` Thomas Petazzoni [this message]
2014-08-04 8:00 ` [Buildroot] [PATCH 0/5 v4] Introduction of kconfig-package (branch yem/patrickdp/kconfig-pkg) Thomas Petazzoni
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=20140804100115.6739393e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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