From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Developer Day, 29th October 2010
Date: Wed, 24 Nov 2010 14:43:27 +0100 [thread overview]
Message-ID: <871v6a7s74.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201011232302.19225.yann.morin.1998@anciens.enib.fr> (Yann E. MORIN's message of "Tue, 23 Nov 2010 23:02:19 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@anciens.enib.fr> writes:
Hi,
>> This is a personal report from Thomas Petazzoni. It hasn't been
>> reviewed by the other participants, so they are kindly invited to
>> share their thoughts and corrections.
Yann> Thank you Thomas, it's all good from my PoV.
Here as well.
Yann> So there are to possibilities:
Yann> 1) add those options to crosstool-NG
Yann> 2) have dedicated code in Buildroot to munge crosstool-NG's uClibc's .config
Yann> (yes, the .config for uClibc used by crosstool-NG)
2 is fine by me (we do the same thing for the internal
toolchain). Perhaps we could even reuse the config handling in
toolchain/uClibc/uclibc.mk ?
>> Peter's goal is to gradually replace the Buildroot internal process to
>> build toolchains by Crosstool-NG. He currently imagines a one-year
>> timeframe before phasing out the Buildroot internal process.
Yann> I believe this is a little bit optimistic. What I would say is that in
Yann> a year time, we can switch the _default_ to being to use crosstool-NG,
Yann> but still have the internal mechanism as a backup. Then, I think that
Yann> another 6 months will be needed before we can decide to get rid of the
Yann> internal mechanism altogether.
True.
Yann> Do not forget that for now, crosstool-NG does not support the same set
Yann> of architectures Buildroot does. Also, Buildroot has per-arch patchsets
Yann> which is (for now at least) a no-no in crosstool-NG.
Do you refer to the avr32 stuff or something else?
>> The next Buildroot Developer Day will happen on Monday, 7th February
>> 2011 in Brussels, Belgium. This is just after the FOSDEM conference
>> (http://www.fosdem.org). Interested participants are invited to
>> contact Peter Korsgaard and Thomas Petazzoni.
Yann> Hehe. FOSDEM `11 is coming fast... I'll sure be there!
Great!
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-11-24 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 21:14 [Buildroot] Report from the Buildroot Developer Day, 29th October 2010 Thomas Petazzoni
2010-11-23 22:02 ` Yann E. MORIN
2010-11-24 13:43 ` Peter Korsgaard [this message]
2010-11-25 17:21 ` Sam Ravnborg
2010-11-25 19:55 ` Thomas Petazzoni
2010-11-26 9:23 ` Peter Korsgaard
2010-11-26 12:16 ` Thomas De Schampheleire
2010-11-26 13:45 ` Thomas Petazzoni
2010-11-26 23:23 ` Yann E. MORIN
2010-11-27 17:13 ` Thomas De Schampheleire
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=871v6a7s74.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