From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Open question: remove "toolchain on target" option
Date: Sat, 11 Aug 2012 22:00:39 +0200 [thread overview]
Message-ID: <20120811220039.0547c8f1@skate> (raw)
In-Reply-To: <201208111446.58278.minimod@morethan.org>
Hello Michael,
Le Sat, 11 Aug 2012 14:46:53 -0500,
"Michael S. Zick" <minimod@morethan.org> a ?crit :
> On Sat August 11 2012, Thomas Petazzoni wrote:
> > ?(3) None of the core Buildroot developers seem to care about this,
> > ? ? ?no-one is apparently using/fixing this mechanism.
>
> The only reason I can see in the argument against continuing support.
>
> A target native toolchain is one of the most often required set of
> applications in the after-market embedded world.
What do you call the "after-market embedded world"? Do you mean the
usage of consumer electronic devices for things that go beyond their
original purposes, by hobbyists? If it's the case, then I think we
definitely want to support this use case, but I don't see how this use
case requires a toolchain on the target.
Could you expand a bit on what this use case is, and how it requires
having a toolchain on the target?
Somehow, your e-mail seems to convey some sort of frustration about
Buildroot and/or its developers. What are the problems you are having?
I am really interested in understanding for what reasons Buildroot is
making people unhappy, and see if there are ways to improve that.
Thanks!
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:[~2012-08-11 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 18:21 [Buildroot] Open question: remove "toolchain on target" option Thomas Petazzoni
2012-08-11 18:44 ` Richard Braun
2012-08-11 19:46 ` Michael S. Zick
2012-08-11 20:00 ` Thomas Petazzoni [this message]
2012-08-12 5:06 ` Jonathan Liu
2012-08-12 5:13 ` Charles Krinke
2012-08-15 9:56 ` Michael S. Zick
2012-08-15 10:39 ` Alex Bradbury
2012-08-15 15:39 ` 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=20120811220039.0547c8f1@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