Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain: binutils external-toolchain gcc uClibc
Date: Mon, 30 Mar 2009 20:58:34 +0200	[thread overview]
Message-ID: <87prfyald1.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090330175842.1960fed2@surf> (Thomas Petazzoni's message of "Mon\, 30 Mar 2009 17\:58\:42 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 >> 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.

 Thomas> The best option would be to compute automatically these
 Thomas> configuration options when using an external toolchain. But I
 Thomas> don't see how this can be done with how the kconfig system
 Thomas> works.

Not without running some kind of configure script to append Kconfig
settins when you're using an external toolchain. I don't quite know
how to integrate this nicely though.

 Thomas> Does something like :

 Thomas> config BR2_ENABLE_LOCALE bool "Enable locale" if
 Thomas> BR2_TOOLCHAIN_BUILDROOT bool "Is locale enabled in your
 Thomas> toolchain ?" if BR2_TOOLCHAIN_EXTERNAL

 Thomas> works ?

Unfortunately not - That's the problem.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2009-03-30 18: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
2009-03-30 16:39       ` Thiago A. Corrêa
2009-03-30 18:58       ` Peter Korsgaard [this message]
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=87prfyald1.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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