diff options
author | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2009-04-28 21:12:23 +0000 |
---|---|---|
committer | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2009-04-28 21:12:23 +0000 |
commit | c9adae97af0f71289da0c1c543de4f52ea8a5b64 (patch) | |
tree | 6e3c896e9bb91a84f497f371fc9248e6c1869eab | |
parent | b7b6946b56219c09c72d6fe3f583333f42a2b05c (diff) |
New section on external toolchain usage
-rw-r--r-- | docs/buildroot.html | 39 |
1 files changed, 38 insertions, 1 deletions
diff --git a/docs/buildroot.html b/docs/buildroot.html index ff8c4ca65..f406b8210 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -36,6 +36,7 @@ same buildroot source tree</a></li> <li><a href="#using_toolchain">Using the uClibc toolchain outside Buildroot</a></li> + <li><a href="#external_toolchain">Use an external toolchain</a></li> <li><a href="#downloaded_packages">Location of downloaded packages</a> </li> <li><a href="#add_software">Extending Buildroot with more @@ -840,7 +841,43 @@ ln -s <shared download location> dl export BUILDROOT_DL_DIR <shared download location> </pre> - + <h2><a name="external_toolchain" id="external_toolchain"></a>Using + an external toolchain</h2> + +<p>It might be useful not to use the toolchain generated by +Buildroot, for example if you already have a toolchain that is known +to work for your specific CPU, or if the toolchain generation feature +of Buildroot is not sufficiently flexible for you (for example if you +need to generate a system with <i>glibc</i> instead of +<i>uClibc</i>). Buildroot supports using an <i>external +toolchain</i>.</p> + +<p>To enable the use of an external toolchain, go in the +<code>Toolchain</code> menu, and :</p> + +<ul> + <li>Select the <code>External binary toolchain</code> toolchain + type</li> + <li>Adjust the <code>External toolchain path</code> + appropriately. It should be set to a path where a bin/ directory + contains your cross-compiling tools</li> + <li>Adjust the <code>External toolchain prefix</code>, so that the + prefix, suffixed with <code>-gcc</code> or <code>-ld</code> will + correspond to your cross-compiling tools</li> +</ul> + +<p>If you are using an external toolchain based on <i>uClibc</i>, the +<code>Core C library from the external toolchain</code> and +<code>Libraries to copy from the external toolchain</code> options +should already have correct values. However, if your external +toolchain is based on <i>glibc</i>, you'll have to change these values +according to your cross-compiling toolchain.</p> + +<p>To generate external toolchains, we recommend using <a +href="http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool">Crosstool-NG</a>. +It allows to generate 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> <h2><a name="add_software" id="add_software"></a>Extending Buildroot with more software</h2> |