From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain: binutils external-toolchain gcc uClibc
Date: Mon, 30 Mar 2009 17:58:42 +0200 [thread overview]
Message-ID: <20090330175842.1960fed2@surf> (raw)
In-Reply-To: <87ab73azsj.fsf@macbook.be.48ers.dk>
Le Mon, 30 Mar 2009 15:46:52 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> The change was done by Daniel Laird back in January (r25170), and was
> afaik because the options for external toolchains weren't in sync with
> the ones for internal toolchains (WCHAR or LIBSTDCPP or something like
> that missing), which meant that the packages depending on those
> toolchain options couldn't be selected in kconfig.
Ok, got it.
> Now, the current approach is certainly nice from a maitenance POV as
> there's only one set of options so they are always in sync, but I
> agree that it isn't that userfriendly.
The best option would be to compute automatically these configuration
options when using an external toolchain. But I don't see how this can
be done with how the kconfig system works.
Does something like :
config BR2_ENABLE_LOCALE
bool "Enable locale" if BR2_TOOLCHAIN_BUILDROOT
bool "Is locale enabled in your toolchain ?" if BR2_TOOLCHAIN_EXTERNAL
works ?
Thomasa
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-03-30 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 16:28 [Buildroot] svn commit: trunk/buildroot/toolchain: binutils external-toolchain gcc uClibc laird at uclibc.org
2009-03-30 13:32 ` Thomas Petazzoni
2009-03-30 13:46 ` Peter Korsgaard
2009-03-30 15:58 ` Thomas Petazzoni [this message]
2009-03-30 16:39 ` Thiago A. Corrêa
2009-03-30 18:58 ` Peter Korsgaard
2009-03-30 19:56 ` Thiago A. Corrêa
2009-03-31 23:28 ` Thomas Petazzoni
2009-04-01 2:43 ` Thiago A. Corrêa
2009-04-02 0:56 ` Hamish Moffatt
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=20090330175842.1960fed2@surf \
--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 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.