Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] docs: Add customizing toolchain section
Date: Thu, 9 Feb 2012 00:15:15 +0100	[thread overview]
Message-ID: <201202090015.15668.arnout@mind.be> (raw)
In-Reply-To: <1328739654-7585-1-git-send-email-s.martin49@gmail.com>

On Wednesday 08 February 2012 23:20:54 Samuel MARTIN wrote:
> 
> Signed-off-by: Samuel MARTIN <s.martin49@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

 Documentation updates, we need more of those!  Thanks, Samuel.

[snip]
> +Using the internal Buildroot toolchain backend
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +The internal Buildroot toolchain backend *only* allows to generate
> +*http://www.uclibc.org/[uClibc]-based toolchains*.
> +
> +However, it allows to tune major settings, such as:
> +
> +* Linux header version
> +
> +* http://www.uclibc.org/[uClibc] configuration (see xref:uclibc-custom[uClibc])
> +
> +* Binutils, GCC, Gdb and toolchain options
> +
> +This is directly avaiblable after selecting the +Buildroot toolchain+ type in
> +the menu +Toolchain+.

Then, the toolchain can be finely tuned invoking +make uclibc-menuconfig+.

:-)

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-02-08 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 22:20 [Buildroot] [PATCH 1/1] docs: Add customizing toolchain section Samuel MARTIN
2012-02-08 23:15 ` Arnout Vandecappelle [this message]
2012-02-09  7:38 ` Thomas De Schampheleire
2012-02-09 22:24 ` Peter Korsgaard

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=201202090015.15668.arnout@mind.be \
    --to=arnout@mind.be \
    --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