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] manual: Add Section on using Buildroot's Toolchain Externally
Date: Thu, 20 Mar 2014 02:58:44 +0100	[thread overview]
Message-ID: <20140320025844.12fa4f78@skate> (raw)
In-Reply-To: <1395273466-19365-1-git-send-email-alan@signal11.us>

Dear Alan Ott,

On Wed, 19 Mar 2014 19:57:46 -0400, Alan Ott wrote:
> Signed-off-by: Alan Ott <alan@signal11.us>
> ---
>  docs/manual/customize-toolchain.txt | 30 ++++++++++++++++++++++++++++++
>  1 file changed, 30 insertions(+)
> 
> diff --git a/docs/manual/customize-toolchain.txt b/docs/manual/customize-toolchain.txt
> index 31c9140..71687d3 100644
> --- a/docs/manual/customize-toolchain.txt
> +++ b/docs/manual/customize-toolchain.txt
> @@ -49,3 +49,33 @@ It allows to tune major settings, such as:
>  
>  These settings are available after selecting the +Buildroot toolchain+ type in
>  the menu +Toolchain+.
> +
> +Using a Buildroot Toolchain from Outside Buildroot
> +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Thanks a lot for this contribution. However, the manual already has a
section about this topic, see:

  http://buildroot.org/downloads/manual/manual.html#_using_the_generated_toolchain_outside_buildroot

Maybe it should be extended to contain more details, but at least it
would be nice to not duplicate the information in the manual.

Thanks a lot!

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

  reply	other threads:[~2014-03-20  1:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 23:57 [Buildroot] [PATCH] manual: Add Section on using Buildroot's Toolchain Externally Alan Ott
2014-03-20  1:58 ` Thomas Petazzoni [this message]
2014-03-20  2:07   ` Alan Ott
2014-03-20 17:56   ` Yann E. MORIN

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=20140320025844.12fa4f78@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