NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

documentation: update buildroot internal toolchain usage

Browse Source 
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
This commit is contained in:
Gustavo Zacarias 2011-02-02 10:05:57 -03:00 committed by Peter Korsgaard
parent a2b4f7fbbd
commit dc5e4ca076
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/buildroot.html
View File

@ -618,8 +618,8 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured
use the toolchain that was generated by Buildroot.</p>
<p>The toolchain generated by Buildroot is located by default in
<code>output/staging/</code>. The simplest way to use it is to add
<code>output/staging/usr/bin/</code> to your PATH environment variable and
<code>output/host/</code>. The simplest way to use it is to add
<code>output/host/usr/bin/</code> to your PATH environment variable and
then to use <code>ARCH-linux-gcc</code>, <code>ARCH-linux-objdump</code>,
<code>ARCH-linux-ld</code>, etc.</p>
@ -628,8 +628,8 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured
is called to tell where the libraries and header files are.</p>
<p>It is also possible to generate the Buildroot toolchain in a
directory other than <code>output/staging</code> by using the <code>
Build options -&gt; Toolchain and header file location</code> options.
directory other than <code>output/host</code> by using the <code>
Build options -&gt; Host dir</code> option.
This could be useful if the toolchain must be shared with other users.</p>
<h2 id="ccache-support">Using <code>ccache</code> in Buildroot</h2>