All of 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: Sat, 23 Jun 2007 11:39:28 +0200	[thread overview]
Message-ID: <20070623093927.GG4096@aon.at> (raw)
In-Reply-To: <01c301c7b519$52679b40$6e02a8c0@k2>

On Fri, Jun 22, 2007 at 05:04:35PM -0500, Rick Foos wrote:
>Hi All,
>
>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.
>
>Is there a problem with restoring "_defconfig" file loading?

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.
>
>I searched the list archives on defconfig, but could not find any decision 
>on this.

http://busybox.net/cgi-bin/viewcvs.cgi/trunk/buildroot/Makefile
revision 16763
>
>The following patch, restores "_defconfig" file loading limited to files at 
>a maxdepth of 4.
>
>This allows "_defconfig" files in packages and tools while avoiding the 
>_defconfig files in the linux source directories.
>
>The patch also fixes the find syntax, and allows "_defconfig" files to be in 
>the same directory as make.
>
>I'd like to propose that this patch be added, or let me know a better way to 
>manage multiple default configurations.

What is this _defconfig thing supposed to do? Please give an example of
what this accomplishes and how it does this.

  reply	other threads:[~2007-06-23  9:39 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 [this message]
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
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=20070623093927.GG4096@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 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.