From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 5] toolchain-external: allow downloading a custom toolchain
Date: Wed, 21 Sep 2011 09:58:43 +0200 [thread overview]
Message-ID: <20110921095843.453ca812@skate> (raw)
In-Reply-To: <d181fc061658f56665ec.1316588132@localhost6.localdomain6>
Le Wed, 21 Sep 2011 08:55:32 +0200,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
> Custom external toolchains currently already have to be extracted by the user.
> This patch adds support for downloading a custom toolchain in the form of a
> tarball, which will be extracted by buildroot.
I like this feature, but I think I'd prefer to clearly separate the
cases of "local custom toolchain" and "remote custom toolchain".
So, in the toolchain choice :
* All the CodeSourcery toolchains
* Local custom toolchain
* Remote custom toolchain
When Local custom toolchain is selected, show :
* Path of the toolchain
* Prefix of the toolchain
When Remote custom toolchain is selected, show :
* URL of the toolchain tarball (please don't split site and source in
the configuration, we don't do that in any other place in Buildroot,
and it's really strange for the user to have to split the URL in two
parts)
* Prefix of the toolchain
What do you think ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-21 7:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 6:55 [Buildroot] [PATCH 0 of 5] toolchain-external: improve support for custom toolchains Thomas De Schampheleire
2011-09-21 6:55 ` [Buildroot] [PATCH 1 of 5] Support URI schemes in DOWNLOAD function, when not using gentargets Thomas De Schampheleire
2011-09-21 6:55 ` [Buildroot] [PATCH 2 of 5] toolchain-external: allow downloading a custom toolchain Thomas De Schampheleire
2011-09-21 7:58 ` Thomas Petazzoni [this message]
2011-09-21 8:22 ` Thomas De Schampheleire
2011-09-21 8:23 ` Thomas De Schampheleire
2011-09-21 11:39 ` Thomas Petazzoni
2011-09-21 11:38 ` Thomas Petazzoni
2011-09-21 6:55 ` [Buildroot] [PATCH 3 of 5] toolchain-external: allow specifying extra external libraries Thomas De Schampheleire
2011-09-21 7:59 ` Thomas Petazzoni
2011-09-21 8:24 ` Thomas De Schampheleire
2011-09-22 19:07 ` Thomas Petazzoni
2011-09-21 6:55 ` [Buildroot] [PATCH 4 of 5] tar: create a host version Thomas De Schampheleire
2011-09-21 6:55 ` [Buildroot] [PATCH 5 of 5] toolchain-external: use host-tar instead of tar to unpack toolchains Thomas De Schampheleire
2011-09-21 8:02 ` Thomas Petazzoni
2011-09-21 8:35 ` Thomas De Schampheleire
2011-09-21 10:54 ` Michael S. Zick
2011-09-21 12:16 ` Thomas De Schampheleire
2011-09-22 20:02 ` Arnout Vandecappelle
2011-09-23 6:18 ` Thomas De Schampheleire
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=20110921095843.453ca812@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