[Buildroot] Make the top rule %_defconfig work

[Buildroot] Make the top rule %_defconfig work

[Hans-Christian Egtvedt]

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 

[Buildroot] Make the top rule %_defconfig work

[Bernhard Fischer]

On Mon, Jun 25, 2007 at 11:27:47AM +0200, Hans-Christian Egtvedt wrote:
>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.

Applied. Thanks!