[Buildroot] [git commit master 1/1] documentation: Mention which external toolchains we tested

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Wed Nov 24 15:40:28 UTC 2010


commit: http://git.buildroot.net/buildroot/commit/?id=5cf1ce9b62f11715fcee1883aef19ccb685cab5a
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
---
 docs/buildroot.html |   11 ++++++-----
 1 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/docs/buildroot.html b/docs/buildroot.html
index aed3856..9ea0374 100644
--- a/docs/buildroot.html
+++ b/docs/buildroot.html
@@ -748,11 +748,12 @@ endif
       correspond to your cross-compiling tools</li>
     </ul>
 
-    <p>To generate external toolchains, we recommend using
-    <a href="http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool">Crosstool-NG</a>.
-    It allows generating toolchains based on <i>uClibc</i>, <i>glibc</i>
-    and <i>eglibc</i> for a wide range of architectures and has good
-    community support.</p>
+    <p>Our external toolchain support has been tested with toolchains
+    from CodeSourcery, toolchains generated
+    by <a href="http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool">Crosstool-NG</a>,
+    and toolchains generated by Buildroot itself. In general, all
+    toolchains that support the <i>sysroot</i> feature should
+    work. If not, do not hesitate to contact the developers.</p>
 
     <h2 id="add_packages">Adding new packages to Buildroot</h2>
 
-- 
1.7.2.2



More information about the buildroot mailing list