| | 59 | |
| | 60 | [=#toolchain] |
| | 61 | == Using Buildroot toolchain externally |
| | 62 | Buildroot builds its own GCC toolchain and using this externally can be useful. The toolchain generated by Buildroot is located by default in {{{output/host/}}} and the simplest way to use it to to add {{{output/host/bin/}}} to your PATH then and use the version of gcc tools there. |
| | 63 | |
| | 64 | For example: |
| | 65 | {{{#!bash |
| | 66 | export PATH=$PWD/output/host/bin:$PATH |
| | 67 | export CROSS_COMPILE=arm-linux- |
| | 68 | export ARCH=arm |
| | 69 | }}} |
| | 70 | |
| | 71 | It is possible to relocate this toolchain making it easy for distribution using {{{make sdk}}} which prepares the toolchain to be relocatable and creates a tarball in the {{{output/host/}}} directory. The {{{relocate-sdk.sh}}} script in the tarball can be used to update paths. |
| | 72 | |
| | 73 | See the full documentation in docs/manual/using-buildroot-toolchain.txt |