Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can "make <>_defconfig" rules be restored?
Date: Mon, 25 Jun 2007 15:40:08 +0200	[thread overview]
Message-ID: <20070625134008.GA7287@aon.at> (raw)
In-Reply-To: <1182777605.10703.37.camel@localhost.localdomain>

On Mon, Jun 25, 2007 at 03:20:05PM +0200, Hans-Christian Egtvedt wrote:
>On Mon, 2007-06-25 at 15:08 +0200, Ulf Samuelsson wrote:
>> > >>
>> > >>I would like to use "_defconfig" files to save and restore specific 
>> > >>defaults
>> > >>for several platforms.
>> > >>
>> > >>The Makefile at one point supported loading of user defined "_defconfig"
>> > >>files. In the current Makefile the noconfig_targets part of "_defconfig" 
>> > >>is
>> > >>commented out.
>> > >>
>> > >
>> > > Yes, the problem with this kind of _defconfig was that in a tree that
>> > > had already one or two compiled arches lying around, the find was the
>> > > cause for a delay in the order of several minutes on my box.
>> > The purpose of this patch is to have several arches lying around.
>> > 
>> It is not particularily efficient to search the whole tree for config files.

That whole quirk is not efficient, that's why i don't use it but have my
configs separarately and do a simple
'make reconfigure CONFIG_DEFCONFIG=/my/foo-config'

As long as you folks don't slow down my testsuite like that (")??=% find
invocation did, i'm happy. That %_defconfig thing is something that i do
not want (and do not want to understand either), and as it doesn't hurt
me and complicates maintenance (which it doesn't from my POV), then it's
fine to apply.

I'm attaching the hunk that i am using to do something like you guy seem
to be up to (or perhaps not, dunno) for your amusement. No find, no ugly
separate dirs that reside in svn, nothing disturbing, just simply does
what it's supposed to do, and doesn't add any bloat or creeping
featureitis. I'll shut up for now.

cheers,
>
>The target/ directory is not that big on my snapshot (although 1 month
>old):
>
>: hcegtvedt at hcegtvedt ~/gitwork/buildroot > find target | wc -l
>554
>: hcegtvedt at hcegtvedt ~/gitwork/buildroot > du -sh target 
>6,3M    target
>
>
>> In my private implementation, I only use the "configs" directory for
>> storage of such files.
>
>Where is the configs directory, under target/configs/ ?
>
>> make B=<board> board
>
>Much like the
>make <board>_defconfig
>make
>
>procedure would do.
>
>> will copy the latest version (they are stored as <board>-<date>.config)
>> to .config.
>
>I.e. the save_config makefile target you talked about?
>
>> The implementation is simplistic.
>> Copy ALL the files to .confiug, so the latest file will overwrite all other files.
>
>-- 
>Mvh
>Hans-Christian Egtvedt
>
>_______________________________________________
>buildroot mailing list
>buildroot at uclibc.org
>http://busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: buildroot-reconfigure.patch
Type: text/x-diff
Size: 797 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070625/5cf2127c/attachment-0001.bin 

  reply	other threads:[~2007-06-25 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 22:04 [Buildroot] Can "make <>_defconfig" rules be restored? Rick Foos
2007-06-23  9:39 ` Bernhard Fischer
2007-06-24  2:12   ` Rick Foos
2007-06-25 13:08     ` Ulf Samuelsson
2007-06-25 13:20       ` Hans-Christian Egtvedt
2007-06-25 13:40         ` Bernhard Fischer [this message]
2007-06-25 13:43           ` Bernhard Fischer
2007-06-25 14:29             ` Rick Foos
2007-06-25 14:42           ` Ulf Samuelsson
2007-06-25 14:02         ` Ulf Samuelsson

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=20070625134008.GA7287@aon.at \
    --to=rep.dot.nop@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox