From 43d7e91f28b15927b2794c31da88e65b2d5f14fc Mon Sep 17 00:00:00 2001 From: Thomas Petazzoni Date: Sun, 30 Jan 2011 15:37:45 +0100 Subject: [PATCH] Explain why we don't support ELDK toolchains. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard --- docs/buildroot.html | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/docs/buildroot.html b/docs/buildroot.html index a5444cc42c..3a7684d30f 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -740,6 +740,31 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured toolchains that support the sysroot feature should work. If not, do not hesitate to contact the developers.

+

We do not support toolchains from + the ELDK of Denx, + for two reasons:

+ +
    + +
  • The ELDK does not contain a pure toolchain (i.e just the + compiler, binutils, the C and C++ libraries), but a toolchain + that comes with a very large set of pre-compiled libraries and + programs. Therefore, Buildroot cannot import the sysroot + of the toolchain, as it would contain hundreds of megabytes of + pre-compiled libraries that are normally built by + Buildroot.
    • + +
  • The ELDK toolchains have a completely non-standard custom + mechanism to handle multiple library variants. Instead of using + the standard GCC multilib mechanism, the ARM ELDK uses + different symbolic links to the compiler to differentiate + between library variants (for ARM soft-float and ARM VFP), and + the PowerPC ELDK compiler uses a CROSS_COMPILE + environment variable. This non-standard behaviour makes it + difficult to support ELDK in Buildroot.
    • + +
+

Adding new packages to Buildroot

This section covers how new packages (userspace libraries or -- 2.30.2