From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] Make savedefconfig save to a configured file.
Date: Wed, 06 Feb 2013 11:15:18 -0300 [thread overview]
Message-ID: <51126576.3090303@zacarias.com.ar> (raw)
In-Reply-To: <41e27bc2d2881606d1da299f6056d24bc9d34e78.1360084128.git.arnout@mind.be>
On 02/05/2013 02:16 PM, Arnout Vandecappelle (Essensium/Mind) wrote:
> source "arch/Config.in"
>
> +config BR2_DEFCONFIG_FROM_ENV
> + string
> + option env="BR2_DEFCONFIG"
> +
> +config BR2_DEFCONFIG
> + string "Location to save buildroot config"
> + default BR2_DEFCONFIG_FROM_ENV if BR2_DEFCONFIG_FROM_ENV != ""
> + default "$(CONFIG_DIR)/defconfig"
> + help
> + When running 'make savedefconfig', the defconfig file will be saved
> + in this location.
> +
> menu "Build options"
Any particular reason for this option to be on the toplevel menu?
It looks terrible there :)
Maybe build options?
Regards.
prev parent reply other threads:[~2013-02-06 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 17:15 [Buildroot] [pull request v4] Pull request for branch arnout-update-config Arnout Vandecappelle
2013-02-05 17:15 ` [Buildroot] [PATCH 1/4] manual: add section about storing the configuration Arnout Vandecappelle
2013-02-05 20:04 ` Peter Korsgaard
2013-02-05 17:16 ` [Buildroot] [PATCH 2/4] target/generic: add filesystem overlay option Arnout Vandecappelle
2013-02-05 20:37 ` Peter Korsgaard
2013-02-05 21:28 ` Arnout Vandecappelle
2013-02-05 17:16 ` [Buildroot] [PATCH 3/4] busybox: busybox-update-config should depend on busybox-configure Arnout Vandecappelle
2013-02-05 20:38 ` Peter Korsgaard
2013-02-05 17:16 ` [Buildroot] [PATCH 4/4] Make savedefconfig save to a configured file Arnout Vandecappelle
2013-02-05 20:43 ` Peter Korsgaard
2013-02-06 14:15 ` Gustavo Zacarias [this message]
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=51126576.3090303@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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.