Commit dc5e4ca0 authored by Gustavo Zacarias's avatar Gustavo Zacarias Committed by Peter Korsgaard
Browse files

documentation: update buildroot internal toolchain usage 



Signed-off-by: default avatarGustavo Zacarias <gustavo@zacarias.com.ar>
Acked-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: default avatarPeter Korsgaard <jacmet@sunsite.dk>
parent a2b4f7fb

docs/buildroot.html

+4 −4
Original line number Diff line number Diff line
@@ -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>