[Buildroot] [PATCH 0 of 7] Introduction of kconfig-package infrastructure

[Jeremy Rosen <jeremy.rosen@openwide.fr>]

----- Mail original -----
> Hi Jeremy,
> 
> On Thu, Jul 31, 2014 at 8:57 AM, Jeremy Rosen
> <jeremy.rosen@openwide.fr> wrote:
> >
> > Quick question... is it possible to relocate the .config file
> > elsewhere using env variables ? I am still on my quest to move
> > all project specific files (i.e configuration files) out of the
> > buildroot directory to be able to build a buildroot project
> > without touching the main buildroot directory...
> 
> Do you really mean the .config file (the destination file) or do you
> mean the file that contains the starting configuration, and that may
> be updated with foo-update-config ?
> 

I don't like the way you have to separately save your kernel configuration
after editing it (update after menuconfig) i'd rather not have to do 
that, but that's the general buildroot philosophy, so i'll follow it

so yes, what I want is the config file that will eventually be used
by buildroot.


> For the latter, individual packages provide config options for this,
> for example uclibc and busybox do. You can specify UCLIBC_CONFIG_FILE
> on the command line to overwrite it, similarly for
> BUSYBOX_CONFIG_FILE.
> 

If these are overloadable from the command line, I should be good, thx

> Best regards,
> Thomas
>