Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Developer Day
Date: Mon, 7 Nov 2011 13:39:02 +0100	[thread overview]
Message-ID: <20111107133902.416ccf35@skate> (raw)
In-Reply-To: <CAAXf6LV8pXKtNqU5oey_yikX_7YMLLVJpd9aE9SpyCgiuCC7zw@mail.gmail.com>

Le Mon, 7 Nov 2011 10:58:22 +0100,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :

> > This report has been written by Thomas Petazzoni, with reviews and
> > comments of Yann E. Morin and Peter Korsgaard. It has been written
> > after the developer day based on memory and raw notes and may
> > therefore be slightly inaccurate in places.
> 
> Also from me, thanks a lot for writing this...

I hope that was useful. Unfortunately, not many Buildroot
users/developers could join, and I really want the community to be
involved in the various decisions, so I felt it was necessary to
provide an extensive report, including our discussions and arguments
for the various decisions.

> > We have therefore decided to make the crosstool-NG backend the
> > default toolchain build mechanism in 2012.02. This will be notified
> > in the 2011.11 release. For the moment, the internal build
> > mechanism will remain available.
> 
> One thing I really like about the internal build mechanism is that
> it's internal. If you want to modify something about it, you can
> directly patch the code and submit to the list.

Right. For crosstool-NG you can also patch the code and submit to the
crosstool-NG list. However I agree that some additional steps are
needed, but we think that the advantage of factorizing the toolchain
build problem in crosstool-NG is much stronger than the drawback you're
mentioning.

> This not only holds for the generation of the toolchain, but also for
> side-aspects like downloading the necessary tarballs and patching.
> Since crosstool-ng is treated as a package (at least currently it
> is), any change you want to make to it, has to be done by adding a
> patchfile to package/crosstool-ng/. This is much more cumbersome than
> modifying buildroot files.
> For example, I added scp support to buildroot some time ago, and use
> it for the primary download site. When switching to crosstool-ng, this
> no longer worked, I had to add scp support again.
> 
> I think it would be beneficial to buildroot if the integration of
> crosstool-ng could increase. For example, crosstool-ng using the
> download mechanisms of buildroot.

That could be discussed with Yann. I'm not sure how this could work
practically, though.

> > Next Buildroot Developer Day
> > ============================
> >
> > The next Buildroot Developer Day will take place on Friday, 3rd
> > February 2012 in Brussels, Belgium. The FOSDEM conference
> > <http://www.fosdem.org> will take place in Brusells on Saturday and
> > Sunday. All Buildroot developers and users are invited to join. The
> > exact location will be given later, but it will be a location in
> > Brussels center, accessible by metro.
> 
> Great, I hope to be able to join this time.

Great!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2011-11-07 12:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 15:03 [Buildroot] Report from the Buildroot Developer Day Thomas Petazzoni
2011-11-02 20:15 ` Peter Korsgaard
2011-11-04 11:56 ` Luca Ceresoli
2011-11-04 12:30   ` Michael S. Zick
2011-11-07 16:17   ` Peter Korsgaard
2011-11-07  9:58 ` Thomas De Schampheleire
2011-11-07 12:09   ` Sam Ravnborg
2011-11-07 12:25     ` Thomas Petazzoni
2011-11-07 12:39       ` Yann E. MORIN
2011-11-08 13:20         ` Thomas De Schampheleire
2011-11-07 12:39   ` Thomas Petazzoni [this message]
2011-11-07 19:01     ` Yann E. MORIN
2011-11-08  8:19       ` Thomas De Schampheleire
2011-11-15 22:17 ` Arnout Vandecappelle
2011-11-15 23:28   ` Michael S. Zick
2011-11-17 13:57   ` Thomas De Schampheleire
2011-11-17 21:21     ` Bjørn Forsman
2011-11-18  6:39       ` Thomas De Schampheleire
2011-11-18 11:04         ` Bjørn Forsman
2011-11-18 11:36           ` Thomas De Schampheleire
2011-11-18 17:51           ` Arnout Vandecappelle
2011-11-18 22:53             ` Peter Korsgaard
2011-11-18 23:16               ` Arnout Vandecappelle
2011-11-19  8:24                 ` Peter Korsgaard
2011-11-20  8:36             ` Thomas Petazzoni
2011-11-20  9:58               ` 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=20111107133902.416ccf35@skate \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox