path: root/docs
diff options
authorGravatar Daniel Serpell <daniel.serpell@gmail.com>2018-02-18 11:50:42 -0300
committerGravatar Thomas Petazzoni <thomas.petazzoni@bootlin.com>2018-02-25 23:26:28 +0100
commitd61e4ad9ef0a1db7cc6d5356ba6d9f08b54c964d (patch)
treef9057e7d59fe969971195793976dd07856f1ac82 /docs
parent2b170210c9bfa70c6c1eae9cc2bc65b03ec9dd6d (diff)
docs/manual: add documentation for the "make sdk" target
Signed-off-by: Daniel Serpell <daniel.serpell@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Diffstat (limited to 'docs')
1 files changed, 11 insertions, 7 deletions
diff --git a/docs/manual/using-buildroot-toolchain.txt b/docs/manual/using-buildroot-toolchain.txt
index 6a90645649..3246dc2411 100644
--- a/docs/manual/using-buildroot-toolchain.txt
+++ b/docs/manual/using-buildroot-toolchain.txt
@@ -12,11 +12,15 @@ The toolchain generated by Buildroot is located by default in
+output/host/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 possible to relocate the toolchain, this allows to distribute
+the toolchain to other developers to build applications for your
+target. To achieve this:
+* run +make sdk+, which prepares the toolchain to be relocatable;
+* tarball the contents of the +output/host+ directory;
+* distribute the resulting tarball.
+Once the toolchain is installed to the new location, the user must run
+the +relocate-sdk.sh+ script to make sure all paths are updated with
+the new location.
-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.