summaryrefslogtreecommitdiff
path: root/docs/buildroot.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/buildroot.html')
-rw-r--r--docs/buildroot.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/buildroot.html b/docs/buildroot.html
index 36297e0..b755922 100644
--- a/docs/buildroot.html
+++ b/docs/buildroot.html
@@ -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>