From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 8 Sep 2009 09:31:41 +0200 Subject: [Buildroot] [PATCH 1/5] Remove the "project" feature In-Reply-To: <87d461528h.fsf@macbook.be.48ers.dk> References: <20090908082707.18e19d6e@hcegtvedt.norway.atmel.com> <1252393123.11390.5.camel@bender> <87hbvd52z7.fsf@macbook.be.48ers.dk> <1252394155.13520.2.camel@bender> <87d461528h.fsf@macbook.be.48ers.dk> Message-ID: <20090908093141.7fd72031@surf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Le Tue, 08 Sep 2009 09:23:26 +0200, Peter Korsgaard 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