From dc5e4ca07617b8f28e759d5a22125cc8636001f2 Mon Sep 17 00:00:00 2001 From: Gustavo Zacarias Date: Wed, 2 Feb 2011 10:05:57 -0300 Subject: [PATCH] documentation: update buildroot internal toolchain usage Signed-off-by: Gustavo Zacarias Acked-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard --- docs/buildroot.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/buildroot.html b/docs/buildroot.html index 36297e0992..b755922c59 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.

The toolchain generated by Buildroot is located by default in - output/staging/. The simplest way to use it is to add - output/staging/usr/bin/ to your PATH environment variable and + output/host/. The simplest way to use it is to add + output/host/usr/bin/ to your PATH environment variable and then to use ARCH-linux-gcc, ARCH-linux-objdump, ARCH-linux-ld, etc.

@@ -628,8 +628,8 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured is called to tell where the libraries and header files are.

It is also possible to generate the Buildroot toolchain in a - directory other than output/staging by using the - Build options -> Toolchain and header file location options. + directory other than output/host by using the + Build options -> Host dir option. This could be useful if the toolchain must be shared with other users.

Using ccache in Buildroot

-- 2.30.2