All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Serpell <daniel.serpell@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] docs/manual: add documentation for the "make sdk" target
Date: Sun, 18 Feb 2018 11:50:42 -0300	[thread overview]
Message-ID: <20180218145042.30773-1-daniel.serpell@gmail.com> (raw)

Signed-off-by: Daniel Serpell <daniel.serpell@gmail.com>
---
 docs/manual/using-buildroot-toolchain.txt | 18 +++++++++++-------
 1 file 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.
-- 
2.16.1

                 reply	other threads:[~2018-02-18 14:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180218145042.30773-1-daniel.serpell@gmail.com \
    --to=daniel.serpell@gmail.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.