The cirros image was rebuilt against the 3.13.0-83 kernel, drivers e1000e, igbvf...

[packages/trusty/cirros-testvm.git] / cirros-testvm / src-cirros / buildroot-2015.05 / docs / manual / using-buildroot-toolchain.txt

diff --git a/cirros-testvm/src-cirros/buildroot-2015.05/docs/manual/using-buildroot-toolchain.txt b/cirros-testvm/src-cirros/buildroot-2015.05/docs/manual/using-buildroot-toolchain.txt
new file mode 100644 (file)
index 0000000..9a98628
--- /dev/null
+++ b/cirros-testvm/src-cirros/buildroot-2015.05/docs/manual/using-buildroot-toolchain.txt
@@ -0,0 +1,22 @@
+// -*- mode:doc; -*-
+// vim: set syntax=asciidoc:
+
+==== Using the generated toolchain outside Buildroot
+
+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.