All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external: clarify external toolchain description
Date: Thu, 19 Feb 2015 21:36:18 +0100	[thread overview]
Message-ID: <20150219213618.7bb7a0b4@free-electrons.com> (raw)
In-Reply-To: <13d64548b894fc1b351af2f9bbb861ce230144d0.1424173685.git.baruch@tkos.co.il>

Dear Baruch Siach,

On Tue, 17 Feb 2015 13:48:05 +0200, Baruch Siach wrote:

>  # This package implements the support for external toolchains, i.e
> -# toolchains that have not been produced by Buildroot itself and that
> -# Buildroot can download from the Web or that are already available on
> -# the system on which Buildroot runs. So far, we have tested this
> +# toolchains that have not been produced locally by Buildroot itself and

I am not sure adding "locally" makes the thing clearer: you can very
well produce a toolchain with Buildroot "locally", and then re-use it
in a later Buildroot build as an external toolchain on the same machine.

Maybe we should simply rephrase this as:

  This package implements the support for external toolchains, i.e
  toolchains that are available pre-built, ready to use. Such toolchain
  me either be readily available on the Web (Linaro, Sourcery
  CodeBench, from processor vendors) or may be built with tools like
  Crosstool-NG or Buildroot itself.

Best regards,

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

  reply	other threads:[~2015-02-19 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 11:48 [Buildroot] [PATCH] toolchain-external: clarify external toolchain description Baruch Siach
2015-02-19 20:36 ` Thomas Petazzoni [this message]
2015-02-20  6:37   ` Baruch Siach
2015-02-20  8:02     ` Thomas Petazzoni

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=20150219213618.7bb7a0b4@free-electrons.com \
    --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 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.