From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about external toolchain configuration "options"
Date: Tue, 13 Apr 2010 18:30:21 +0000 (UTC) [thread overview]
Message-ID: <hq2d7t$5ut$1@dough.gmane.org> (raw)
When using an external toolchain, there are a bunch of toolchain
toolchain "configuration options" in the buildroot .config file (e.g.
support for locale/i18n, wchar, ipv6, program_invokation, etc.).
However, these "options" don't really seem to be options.
There's only one correct choice for each, and buildroot figures out
what those correct choices are at build-time and aborts if the user
has picked the wrong values.
Why are they presented to the user as "choices" when the user doesn't
get to choose their values? They only seem to be user-configurable
when building a toolchain. When using an external toolchain, why not
just determine the correct values and do the build?
--
Grant Edwards grant.b.edwards Yow! My NOSE is NUMB!
at
gmail.com
next reply other threads:[~2010-04-13 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 18:30 Grant Edwards [this message]
2010-04-13 18:51 ` [Buildroot] Question about external toolchain configuration "options" Yann E. MORIN
2010-04-14 14:58 ` Thomas Petazzoni
2010-04-14 15:01 ` 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='hq2d7t$5ut$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.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