Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/9] manual: add information about buildroot toolchain not being relocable and put some hints to use it
Date: Sun, 6 Oct 2013 11:08:50 +0200	[thread overview]
Message-ID: <20131006110850.0f584465@skate> (raw)
In-Reply-To: <ef67fc0502d4a0a4cdce65dc850921e08e0cfef0.1381002281.git.s.martin49@gmail.com>

Dear Samuel Martin,

This commit is again mixing a number of different things: removing
details about Crosstool-NG, improving details about the Buildroot
backend, and adding informations on re-using a Buildroot built
toolchain as an external toolchain.

We'll need to synchronize on the Crosstool-NG bits, because I have a
patch series that removes the Crosstool-NG backend entirely, and which
includes the corresponding update to the manual.

On Sat,  5 Oct 2013 21:49:09 +0200, Samuel Martin wrote:

> +It is possible to only build the toolchain by running:
> +
> +---------------------------------------
> +make toolchain
> +---------------------------------------
> +
> +To avoid to rebuild the toolchain (when using the 'internal Buildroot toolchain
> +backend') after executing +make clean+, you can build the toolchain in some
> +place, then use this prebuilt toolchain as an 'external toolchain' in another
> +buildroot configuration.
> +
> +1. Configure the toolchain using the 'internal Buildroot toolchain backend'
> +  to meet your needs:
> ++
> +---------------------------------------
> +make O=/path/to/somewhere menuconfig
> +---------------------------------------
> ++
> +1. Build the toolchain:
> ++
> +---------------------------------------
> +make O=/path/to/somewhere toolchain
> +---------------------------------------
> ++
> +1. Configure target configuration using the prebuilt toolchain as an
> +   'external toolchain':
> ++
> +---------------------------------------
> +make O=/path/to/somewhere_else menuconfig
> +---------------------------------------
> ++
> +In the 'Toolchain' menu, set:
> ++
> +* 'Toolchain type': +External toolchain+ (+BR2_TOOLCHAIN_EXTERNAL+)
> +* 'Toolchain': +Custom toolchain+ (+BR2_TOOLCHAIN_EXTERNAL_CUSTOM+)
> +* 'Toolchain origin': +Pre-installed toolchain+
> +  (+BR2_TOOLCHAIN_EXTERNAL_PREINSTALLED+)
> +* 'Toolchain path': +/path/to/somewhere/host/usr+
> +  (+BR2_TOOLCHAIN_EXTERNAL_PATH+)
> +* and set the external toolchain properties accordingly to the ones set for
> +  the prebuilt toolchain.
> ++
> +1. Build the target binaries:
> ++
> +---------------------------------------
> +make O=/path/to/somewhere_else
> +---------------------------------------
> +
> +Note that toolchains built using the 'internal Buildroot toolchain backend' are
> +*not* relocable, so if you plan to share it with other machines, you will
> +*have to* install it in the same location (i.e.: in +/path/to/somewhere+).

I am not sure this part should be in the "Customize toolchain" part.
I'm actually not sure where to put this information in the manual.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-10-06  9:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05 19:49 [Buildroot] [pull request] Pull request for branch sma/doc-update Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 1/9] manual: minor update in manual generation Samuel Martin
2013-10-06  9:04   ` Thomas Petazzoni
2013-10-06 11:17     ` Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 2/9] manual: developer-guide.txt: cleanup non-existing source Samuel Martin
2013-10-06  9:04   ` Thomas Petazzoni
2013-10-08  7:51   ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 3/9] manual: update dependency list to build the documentation Samuel Martin
2013-10-06  9:05   ` Thomas Petazzoni
2013-10-06 16:25   ` Thomas De Schampheleire
2013-10-06 18:21     ` Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 4/9] manual: add information about buildroot toolchain not being relocable and put some hints to use it Samuel Martin
2013-10-06  9:08   ` Thomas Petazzoni [this message]
2013-10-06 14:50     ` Samuel Martin
2013-10-08  9:03   ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 5/9] manual: configure: add deprecation warning for Crosstool-NG toolchain backend Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 6/9] manual: introduction.txt: enhance Buildroot presentation Samuel Martin
2013-10-08  9:18   ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 7/9] manual: get-involved.txt: fix event order Samuel Martin
2013-10-08  9:31   ` Thomas De Schampheleire
2013-10-08 18:04     ` Arnout Vandecappelle
2013-10-08 18:28       ` Ryan Barnett
2013-10-05 19:49 ` [Buildroot] [PATCH 8/9] manual: update get-involved section Samuel Martin
2013-10-08  9:39   ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 9/9] manual: rework Deploying images chapter Samuel Martin
2013-10-08 20:29   ` Arnout Vandecappelle
2013-10-15 20:27     ` Thomas De Schampheleire
2013-10-16 21:29       ` Arnout Vandecappelle
2013-10-17  8:12         ` Thomas De Schampheleire
2013-10-17  8:18           ` Arnout Vandecappelle
2013-10-17  8:43             ` Samuel Martin
2013-10-17  8:40     ` Samuel Martin
2013-10-17 16:24       ` Arnout Vandecappelle

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=20131006110850.0f584465@skate \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox