jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-29 14:16:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs/manual: rephrase paragraph about unsupported external toolchains

Browse Source 
The ELDK now relies on Yocto, so it no longer has the funky
non-standard way of doing multilib. Also, we didn't mention that Yocto
toolchains/SDK are not suitable for usage with Buildroot. Therefore,
this commit rewords this part of the documentation to explain that
Yocto/OpenEmbedded SDKs cannot be used as external toolchains in
Buildroot, and why.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
Thomas Petazzoni 2014-02-23 16:04:36 +01:00 committed by Peter Korsgaard
parent 3883823614
commit 5e26da4673
1 changed files with 7 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/manual/configure.txt
View File

@ -179,23 +179,13 @@ Buildroot itself. In general, all toolchains that support the
'sysroot' feature should work. If not, do not hesitate to contact the 'sysroot' feature should work. If not, do not hesitate to contact the
developers. developers.
We do not support toolchains from the We do not support toolchains or SDK generated by OpenEmbedded or
http://www.denx.de/wiki/DULG/ELDK[ELDK] of Denx, for two reasons: Yocto, because these toolchains are not pure toolchains (i.e just the
compiler, binutils, the C and C++ libraries). Instead these toolchains
* The ELDK does not contain a pure toolchain (i.e just the compiler, come with a very large set of pre-compiled libraries and
binutils, the C and C++ libraries), but a toolchain that comes with programs. Therefore, Buildroot cannot import the 'sysroot' of the
a very large set of pre-compiled libraries and programs. Therefore, toolchain, as it would contain hundreds of megabytes of pre-compiled
Buildroot cannot import the 'sysroot' of the toolchain, as it would libraries that are normally built by Buildroot.
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.
We also do not support using the distribution toolchain (i.e the We also do not support using the distribution toolchain (i.e the
gcc/binutils/C library installed by your distribution) as the gcc/binutils/C library installed by your distribution) as the