[Buildroot] [PATCH 1/5] Remove the "project" feature
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Tue Sep 8 07:31:41 UTC 2009
Le Tue, 08 Sep 2009 09:23:26 +0200,
Peter Korsgaard <jacmet at uclibc.org> a écrit :
> Yes, something like that. Have you read
> http://buildroot.net/buildroot.html#external_toolchain ? As I said
> before, I haven't actually used it yet, maybe Thomas can fill in the
> blanks?
Until now, I've only used the external toolchain support to use
toolchains compiled with Crosstool-NG. I haven't tried re-using a
toolchain generated by Buildroot. In theory, it shouldn't make any
difference, but everyone knows that between theory and practice,
there's usually a gap.
> 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.
Ah, I'm interested in how you would do that. Currently, what the
external toolchain support does is that:
1. It asks the user for the configuration of the toolchain in the
Kconfig interface (IPV6 ? RPC ? Locale ? WCHAR ? LARGEFILE ?),
because at configuration time, it is not possible to execute tests
to guess the toolchain configuration, but these configuration
options must be defined properly since some packages depend on them.
2. At compilation time, before "importing" the external toolchain,
ext-tool.mk checks the validy of the provided configuration against
the toolchain.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
More information about the buildroot
mailing list