2012-11-11 04:14:42 +01:00
|
|
|
// -*- mode:doc; -*-
|
2013-02-13 13:59:02 +01:00
|
|
|
// vim: set syntax=asciidoc:
|
2012-11-11 04:14:42 +01:00
|
|
|
|
2011-10-10 10:46:39 +02:00
|
|
|
Using the generated toolchain outside Buildroot
|
2012-11-11 04:14:42 +01:00
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
2011-10-10 10:46:39 +02:00
|
|
|
|
|
|
|
|
You may want to compile, for your target, your own programs or other
|
|
|
|
|
software that are not packaged in Buildroot. In order to do this you
|
|
|
|
|
can use the toolchain that was generated by Buildroot.
|
|
|
|
|
|
|
|
|
|
The toolchain generated by Buildroot is located by default in
|
|
|
|
|
+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.
|
|
|
|
|
|
|
|
|
|
It is possible to relocate the toolchain - but then +--sysroot+ must
|
|
|
|
|
be passed every time the compiler 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/host+ by using the +Build options -> Host dir+
|
|
|
|
|
option. This could be useful if the toolchain must be shared with
|
|
|
|
|
other users.
|
