From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 3 v2] uclibc: fix handling of configuration file
Date: Tue, 15 Jul 2014 20:43:34 +0200 [thread overview]
Message-ID: <patchbomb.1405449814@localhost> (raw)
This patch series (part of it poster earlier as RFC) has as main goal to
fix the uclibc kconfig handling with following requirements in mind:
- neither foo-menuconfig nor foo-update-config should have a dependency
on the toolchain (which means we cannot depend on foo-configure)
- 'clean foo-menuconfig' should start from the specified (custom) config
file
- 'foo-menuconfig foo-update-config' should preserve the changes made in
the menuconfig step (this problem is reported for uclibc with bug #7154
(https://bugs.busybox.net/show_bug.cgi?id=7154).
- 'make foo-menuconfig; make foo-menuconfig' should preserve the changes
made in the menuconfig step.
- 'make clean foo-update-config' should copy the initial file, do any
fixups, and then save the config
Once this series is accepted, the plan is:
- to extract the kconfig-related bits to a kconfig-package infrastructure.
- to convert busybox, linux and barebox to this kconfig-package infra too.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
package/uclibc/uclibc.mk | 24 ++++++++++++++++--------
1 files changed, 16 insertions(+), 8 deletions(-)
next reply other threads:[~2014-07-15 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 18:43 Thomas De Schampheleire [this message]
2014-07-15 18:43 ` [Buildroot] [PATCH 1 of 3 v2] uclibc: rename SETUP_DOT_CONFIG to FIXUP_DOT_CONFIG Thomas De Schampheleire
2014-07-17 23:23 ` Arnout Vandecappelle
2014-07-15 18:43 ` [Buildroot] [PATCH 2 of 3 v2] uclibc: menuconfig: take into account initial settings from config file Thomas De Schampheleire
2014-07-15 18:43 ` [Buildroot] [PATCH 3 of 3 v2] uclibc: update-config: preserve freshly configured settings Thomas De Schampheleire
2014-07-17 17:57 ` [Buildroot] [PATCH 0 of 3 v2] uclibc: fix handling of configuration file Thomas De Schampheleire
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=patchbomb.1405449814@localhost \
--to=patrickdepinguin@gmail.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 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.