From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] external toolchain scanner
Date: Mon, 16 Jan 2017 15:54:13 +0100 [thread overview]
Message-ID: <87wpdv9ht6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170116084812.5e7bafeb@free-electrons.com> (Thomas Petazzoni's message of "Mon, 16 Jan 2017 08:48:12 +1100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> But it's probably best to implement the first scenario and see where we go from
>> there.
> To be honest, I find all of this very complicated, and even more
> confusing than what we have today. Using custom external toolchain is
> already an "advanced" feature, which users just getting started with
> Buildroot are unlikely to use. To me, using custom external toolchain
> is a bit of an advanced functionality, and people who need that will
> surely be able to understand the information they need to fill in
> "menuconfig" to make Buildroot "accept" the toolchain.
Yes, I'm also not really sure what realistic use cases this scripts
covers.
>> But perhaps that would be an easier first step. Instead of just reporting one
>> single error, report all errors and the correct config options so the user can
>> edit the .config file and add them.
> Yes. *This* would be useful.
Agreed.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-01-16 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 1:32 [Buildroot] [RFC] external toolchain scanner Hollis Blanchard
2016-11-23 6:23 ` Baruch Siach
2016-12-07 18:14 ` Hollis Blanchard
2016-12-08 21:02 ` Yann E. MORIN
2016-12-19 20:07 ` Hollis Blanchard
2017-01-09 23:07 ` Hollis Blanchard
2017-01-12 17:32 ` Yann E. MORIN
2017-01-12 22:12 ` Hollis Blanchard
2017-01-12 23:43 ` Arnout Vandecappelle
2017-01-15 21:48 ` Thomas Petazzoni
2017-01-16 14:54 ` Peter Korsgaard [this message]
2017-01-16 18:36 ` Hollis Blanchard
-- strict thread matches above, loose matches on Subject: below --
2016-11-23 6:34 Blanchard, Hollis
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=87wpdv9ht6.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.