All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Linux and busybox-configfiles
Date: Wed, 30 Jan 2013 10:54:36 +0100	[thread overview]
Message-ID: <5108EDDC.5050808@mind.be> (raw)
In-Reply-To: <ce1e1f6b-7d56-461e-87a7-d18a64240c35@zimbra2.corp.accelance.fr>

On 30/01/13 08:50, Jeremy Rosen wrote:
>>    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?
>>
>>
>
> I am not sure what you mean by "the configured" vs "the customized"
>
> I guess that the customized is the one from make linux-menuconfig and the configured is the one from make foo_defconfig

  Not from 'make foo_defconfig', but from 'make menuconfig'.

  If in the buildroot config I select 'Use omap2plus defconfig' for the 
kernel, then I expect it to use the omap2plus configuration. Similarly, 
if I set the custom linux config to /some/path/linux.config, then I 
expect that that configuration will be used.

  So 'configured' is what you see in 'make menuconfig', 'customized' is 
what you see in 'make linux-menuconfig'.


> hmm, I see your use case.... I would tend to argue that the kernel is no exception to the way buildroot works
>
> * make clean removes all build-generated but doesn't touch user-defined configurations (BR configuration, kernel configuration)

  But the problem is that the buildroot configuration conflicts with the 
kernel configuration.


  Regards,
  Arnout

> * to revert to BR's suggested configuration, use make xxx_defconfig, and that would override both the kernel and BR's configuration.
>
> I don't really see a use-case for "revert my changes to the kernel, but not the rest of buildroot" though providing targets like make linux-xxx_defconfig for all kernel defined defconfig
> and/or a make linux-buildrootconfig to revert to the buildroot-suggested config might make sense...
>
>
> Best
> J?r?my
>


-- 
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

  reply	other threads:[~2013-01-30  9:54 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 [this message]
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=5108EDDC.5050808@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 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.