From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Linux and busybox-configfiles
Date: Wed, 30 Jan 2013 11:41:40 +0100 [thread overview]
Message-ID: <5108F8E4.2010404@relinux.de> (raw)
In-Reply-To: <f05257cb-b9a4-405c-8e3d-90a0bb017206@zimbra2.corp.accelance.fr>
Am 30.01.2013 11:01, schrieb Jeremy Rosen:
>> But the problem is that the buildroot configuration conflicts with
>> the
>> kernel configuration.
>>
>>
>> Regards,
>> Arnout
>>
>
> aha....
>
> so our problem is that make linux-menuconfig should change the buildroot configuration option from "use defconfig" to "use a custom configuration"
>
> is that it ?
I don't think so. If we regard the buildroot configuration option more
as a starting point for configuring busybox and linux than as the actual
used value, we are right there:
After "make xxx_defconfig" we have the default configuration.
"make xxx-menuconfig" takes us to a temporary "work in progress" point,
where our system no longer matches the default configuration but is
defined by .config, busybox-config and linux-config.
"make xxx_defconfig && make clean" discards all changes and restores the
default configuration.
"make xxx-update-config" updates the config file named in buildroot's
config file constituting a new default.
"make savedefconfig && cp defconfig configs/xxx_defconfig" does the same
for the changes in buildroot's config file.
Maybe it makes sense to change some names?
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE -> BR2_LINUX_KERNEL_DEFAULT_CONFIG_FILE
BR2_PACKAGE_BUSYBOX_CONFIG -> BR2_PACKAGE_BUSYBOX_DEFAULT_CONFIG
Regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
next prev parent reply other threads:[~2013-01-30 10:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 16:08 [Buildroot] Linux and busybox-configfiles Stephan Hoffmann
2013-01-27 16:11 ` [Buildroot] [PATCH 1/2] Busybox: save a copy of the config file Stephan Hoffmann
2013-02-14 17:53 ` Stephan Hoffmann
2013-01-27 16:11 ` [Buildroot] [PATCH 2/2] Linux: " Stephan Hoffmann
2013-02-14 17:51 ` Stephan Hoffmann
2013-01-27 22:36 ` [Buildroot] Linux and busybox-configfiles Arnout Vandecappelle
2013-01-28 7:59 ` Jeremy Rosen
2013-01-28 8:47 ` Stephan Hoffmann
2013-01-29 0:16 ` Shawn J. Goff
2013-01-29 7:57 ` Stephan Hoffmann
2013-01-29 13:45 ` Shawn J. Goff
2013-01-29 17:33 ` Arnout Vandecappelle
2013-01-30 7:50 ` Jeremy Rosen
2013-01-30 9:54 ` Arnout Vandecappelle
2013-01-30 10:01 ` Jeremy Rosen
2013-01-30 10:41 ` Stephan Hoffmann [this message]
2013-01-28 9:16 ` Willy Lambert
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=5108F8E4.2010404@relinux.de \
--to=sho@relinux.de \
--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.