[Buildroot] [PATCH 1/5] Remove the "project" feature

[Peter Korsgaard <jacmet@uclibc.org>]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 Thomas> Until now, I've only used the external toolchain support to use
 Thomas> toolchains compiled with Crosstool-NG. I haven't tried re-using a
 Thomas> toolchain generated by Buildroot. In theory, it shouldn't make any
 Thomas> difference, but everyone knows that between theory and practice,
 Thomas> there's usually a gap.

Yeah ;) I'll give it a try soon and see how it works out.

 >> It might be an idea to get the toolchain build to write out a .config
 >> snippet that can get included when using it to ensure we have the
 >> various toolchain settings correct.

 Thomas> Ah, I'm interested in how you would do that. Currently, what the
 Thomas> external toolchain support does is that:

I was thinking that we maybe could (ab)use the KCONFIG_ALLCONFIG support
stuff for it. From linux/Documentation/kbuild/kconfig.txt:

The allyesconfig/allmodconfig/allnoconfig/randconfig variants can
also use the environment variable KCONFIG_ALLCONFIG as a flag or a
filename that contains config symbols that the user requires to be
set to a specific value.

But I haven't looked at it in detail yet.

 Thomas>  1. It asks the user for the configuration of the toolchain in the
 Thomas>     Kconfig interface (IPV6 ? RPC ? Locale ? WCHAR ? LARGEFILE ?),
 Thomas>     because at configuration time, it is not possible to execute tests
 Thomas>     to guess the toolchain configuration, but these configuration
 Thomas>     options must be defined properly since some packages depend on them.

Yes, that's the step I think we could automate when the toolchain comes
from buildroot.

-- 
Bye, Peter Korsgaard