From: Rick Foos <rick@synchromeshcomputing.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can "make <>_defconfig" rules be restored?
Date: Fri, 22 Jun 2007 17:04:35 -0500 [thread overview]
Message-ID: <01c301c7b519$52679b40$6e02a8c0@k2> (raw)
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?
I searched the list archives on defconfig, but could not find any decision
on this.
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.
Thanks,
Rick Foos
Index: Makefile
===================================================================
--- Makefile (revision 9)
+++ Makefile (working copy)
@@ -28,10 +28,9 @@
noconfig_targets := menuconfig config oldconfig randconfig \
defconfig allyesconfig allnoconfig release tags \
- source-check
+ source-check \
+ $(shell find $(TOPDIR) -mindepth 2 -maxdepth 4 -name \*_defconfig |
sed
's|.*\/||')
-# $(shell find . -name *_defconfig |sed 's/.*\///')
-
# Pull in the user's configuration file
ifeq ($(filter $(noconfig_targets),$(MAKECMDGOALS)),)
-include $(TOPDIR).config
next reply other threads:[~2007-06-22 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 22:04 Rick Foos [this message]
2007-06-23 9:39 ` [Buildroot] Can "make <>_defconfig" rules be restored? 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
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='01c301c7b519$52679b40$6e02a8c0@k2' \
--to=rick@synchromeshcomputing.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.