From 92bfa8fda9aba6d0e8973d9ebd4b93faa89bed6a Mon Sep 17 00:00:00 2001 From: Bernhard Reutner-Fischer Date: Thu, 21 Jun 2007 16:58:36 +0000 Subject: - update docs to mention the new sysroot support. --- docs/buildroot.html | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) (limited to 'docs') diff --git a/docs/buildroot.html b/docs/buildroot.html index f08e2ee8f..6bddd31d6 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -362,7 +362,7 @@ $ make HOSTCXX=g++-4.3-HEAD HOSTCC=gcc-4.3-HEAD default). This is where the cross-compilation toolchain will be installed. If you want to use the same cross-compilation toolchain for other purposes, such as compiling third-party applications, you can add - build_ARCH/staging_dir/bin to your PATH, and then use + build_ARCH/staging_dir/usr/bin to your PATH, and then use arch-linux-gcc to compile your application. In order to setup this staging directory, it first removes it, and then it creates various subdirectories and symlinks inside it. @@ -390,7 +390,7 @@ $ make HOSTCXX=g++-4.3-HEAD HOSTCC=gcc-4.3-HEAD

The toolchain generated by Buildroot by default is located in build_ARCH/staging_dir/. The simplest way to use it - is to add build_ARCH/staging_dir/bin/ to your PATH + is to add build_ARCH/staging_dir/usr/bin/ to your PATH environnement variable, and then to use arch-linux-gcc, arch-linux-objdump, arch-linux-ld, etc.

@@ -401,7 +401,7 @@ $ make HOSTCXX=g++-4.3-HEAD HOSTCC=gcc-4.3-HEAD ~/buildroot/) :

-export PATH="$PATH:~/buildroot/build_mips/staging_dir/bin/"
+export PATH="$PATH:~/buildroot/build_mips/staging_dir/usr/bin/"

Then you can simply do :

@@ -410,12 +410,15 @@ export PATH="$PATH:~/buildroot/build_mips/staging_dir/bin/" mips-linux-gcc -o foo foo.c -

Important : do not try to move the toolchain to an other +

Important : do not try to move a gcc-3.x toolchain to an other directory, it won't work. There are some hard-coded paths in the gcc configuration. If the default toolchain directory doesn't suit your needs, please refer to the Using the uClibc toolchain outside of buildroot section.

+

If you are using a current gcc-4.x, then use --sysroot and -isysroot + since these toolchains have fully functional sysroot support. No + hardcoded paths do exist in these configurations.

Using the uClibc toolchain outside of buildroot

@@ -424,10 +427,11 @@ mips-linux-gcc -o foo foo.c build_ARCH/staging_dir/. But sometimes, it may be useful to install it somewhere else, so that it can be used to compile other programs or by other users. Moving the build_ARCH/staging_dir/ - directory elsewhere is not possible, because they are some hardcoded - paths in the toolchain configuration.

+ directory elsewhere is not possible if using gcc-3.x, because they are some hardcoded + paths in the toolchain configuration. This works, thanks to sysroot support, with current, + stable gcc-4.x toolchains, of course.

-

If you want to use the generated toolchain for other purposes, +

If you want to use the generated gcc-3.x toolchain for other purposes, you can configure Buildroot to generate it elsewhere using the option of the configuration tool : Build options -> Toolchain and header file location, which defaults to -- cgit v1.2.3