From: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Make the top rule %_defconfig work
Date: Mon, 25 Jun 2007 11:27:47 +0200 [thread overview]
Message-ID: <1182763667.10703.21.camel@localhost.localdomain> (raw)
Hi,
Please see the included patch as a comment to the earlier discussion
about having _defconfig. By only searching the target/ directory it will
not conflict with the extracted kernel and similar.
It makes the most sense to be able to load a BR2 <board>_defconfig from
the target directory. What this build target does is to overwrite
the .config with a premade default configuration.
For example as a hardware (and software) provider I would like to be
able to build a "standard" image having a collection of applications
useful for the board.
--
Mvh
Hans-Christian Egtvedt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Search-for-defconfigs-in-target-not-entire-tree.txt
Type: application/mbox
Size: 0 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070625/f14863a8/attachment.bin
next reply other threads:[~2007-06-25 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 9:27 Hans-Christian Egtvedt [this message]
2007-06-25 10:55 ` [Buildroot] Make the top rule %_defconfig work Bernhard Fischer
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=1182763667.10703.21.camel@localhost.localdomain \
--to=hcegtvedt@norway.atmel.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