All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Izard <romain.izard.pro@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/2] core/pkg-kconfig: Fix .config generation
Date: Tue, 29 Mar 2016 12:11:40 +0200	[thread overview]
Message-ID: <1459246302-21837-1-git-send-email-romain.izard.pro@gmail.com> (raw)

To use an existing file as .config for a project, it needs to be
validated with 'make oldconfig'. If the file does not match all the
configuration entries of the project, the user will be prompted to
select the values for the new entries.

Historically, 'yes "" | make oldconfig' was used to silently select the
default values for new entries. But this does not work well with the
Linux kernel, as it will not select the correct option when configuring
tristate choice entries.

The Linux kernel has added a 'oldnoconfig' target, since renamed
'olddefconfig', that will work correctly, but this target does not exist
in all projects that rely on the kconfig workflow.

Update buildroot to use 'oldnoconfig' when available, and fallback to
the default method otherwise.

Romain Izard (2):
  core/pkg-kconfig: fix .config rule for silent mode
  core/pkg-kconfig: Use oldnoconfig when possible

 package/pkg-kconfig.mk | 26 ++++++++++++++++++--------
 1 file changed, 18 insertions(+), 8 deletions(-)

-- 
2.5.0

             reply	other threads:[~2016-03-29 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 10:11 Romain Izard [this message]
2016-03-29 10:11 ` [Buildroot] [PATCH v2 1/2] core/pkg-kconfig: fix .config rule for silent mode Romain Izard
2016-03-29 14:55   ` Thomas Petazzoni
2016-03-29 10:11 ` [Buildroot] [PATCH v2 2/2] core/pkg-kconfig: Use oldnoconfig when possible Romain Izard
2016-03-30 20:30   ` 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=1459246302-21837-1-git-send-email-romain.izard.pro@gmail.com \
    --to=romain.izard.pro@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.