From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Linux and busybox-configfiles
Date: Tue, 29 Jan 2013 18:33:45 +0100 [thread overview]
Message-ID: <510807F9.3040905@mind.be> (raw)
In-Reply-To: <5105ABE8.70409@mind.be>
On 27/01/13 23:36, Arnout Vandecappelle wrote:
> On 27/01/13 17:08, Stephan Hoffmann wrote:
>> Hello all,
>>
>> buildroot provides direct calls to the configuration menus for busybox
>> and linux:
>>
>> make linux-menuconfig
>> make busybox-menuconfig
>>
>> Additionally, there is a linux-savedefconfig make target.
>>
>> All these save their output in the build directory, so that all changes
>> get lost when "make clean" is called. Thus I don't think that I am the
>> only one who has been surprised to notice that "make busybox-menuconfig
>> && make clean && make" does not have any effect on busybox's
>> configuration.
>
> This is a bit a philosophical discussion: should the configuration
> files of linux, busybox, etc. be considered part of the buildroot
> configuration or not? In the former case, they should survive a 'make
> clean', in the latter case they should be removed by 'make clean'.
>
> I tend to agree that the package configs should be considered part of
> the buildroot config. However, if your buildroot config specifies some
> BR2_PACKAGE_BUSYBOX_CONFIG, then I would expect that after 'make clean',
> that is the config that will be used. More generically, I expect I can do:
>
> make foo_defconfig
> Do all kinds of weird stuff that completely messes things up
> make clean
> make
>
> and to be back in the same state as 'make foo_defconfig; make'.
>
>
> Bottom line: I tend to say no to this patch.
After the feedback from Real Users (Stephan, Jeremy, Shawn), it looks
like I have to revise my opinion...
Or are there any other voices against?
If this does go through, I would like to have some way to throw away
the customized config and revert to the configured config. Perhaps a
'realclean' target?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-01-29 17:33 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 [this message]
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
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=510807F9.3040905@mind.be \
--to=arnout@mind.be \
--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