[Buildroot] Can "make <>_defconfig" rules be restored?

Ulf Samuelsson ulf at atmel.com
Mon Jun 25 14:42:12 UTC 2007


> >> 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.

Similar to my stuff.
The reason I use a separate directory, is that I do not want to specify
where the config file is located inside the command to configure.

"make reconfigure
CONFIG_DEFCONFIG=/home/ulf/projects/Buildroot/20070531/buildroot-atmel/configs/at91sam9263-2007-06-25.config"

is just a little more typing than I like.


I prefer the <board>_defconfig syntax, since this is easier
to remember than and there is therefore less likelyhood that errors
occur, I.E: less support calls.

Also the stuff does not easily lend it to updating the config file.
I can save the configuration in a new file, and this is a nice feature
I really like to have.


-- 
Best Regards,
Ulf Samuelsson




More information about the buildroot mailing list