From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Talk at Embedded Linux Conference Europe
Date: Wed, 2 Nov 2011 13:28:49 +0100 [thread overview]
Message-ID: <20111102132849.5713060d@skate> (raw)
In-Reply-To: <CAAXf6LVzd4z5j_Y-w6jXvUCdsmZkgxEqJQtiVG4ZPzDKhdfnjA@mail.gmail.com>
Le Wed, 2 Nov 2011 11:37:30 +0100,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
> > Covering the 40+ slides consumed almost the entire time slot, so
> > there was only time left for a few questions at the end. Generally
> > speaking, I had the feeling that there is definitely an interest in
> > Buildroot, as an alternative to bigger things like OE or Yocto. For
> > example, I went to the Yocto Bird-of-a-Feather session, and the
> > first 20 minutes of the session was spent answering questions of
> > the audience about how Yocto compares to Buildroot, what are the
> > relative advantages/drawbacks, etc.
>
> It's nice to hear about this interest in Buildroot.
> Was there anything in particular that came out of the Yocto vs.
> Buildroot discussion? Things that are seen as a drawback of buildroot
> that we could improve without sacrificing the design goals? Features
> that are found lacking?
You'll be able to watch the video. But basically, the Yocto people were
putting the emphasis on Yocto being a distribution builder, i.e it
builds a set of packages and not just a root filesystem image. But
interestingly, in the room, one of the person said that for his
embedded Linux projects, which are deeply embedded ones (such as
washing machines, or other industrial stuff), packaging is completely
useless and he just wants something that generates a root filesystem
image.
> > The final version of the slides are available at:
> >
> > ?http://elinux.org/images/2/2a/Using-buildroot-real-project.pdf
> >
> > I intend to contribute some of those elements to the official
> > documentation.
>
> I think that would definitely be useful. As several people indicated,
> your write-up of some best practices is very interesting for project
> developers.
Ok, I'll try to work on that. I'm pretty busy until end of November due
to the organization of a free software event in France, but after that,
my free time will again be dedicated to Buildroot stuff.
> > I also would like to thank all the persons who reviewed
> > my slides and maybe very useful comments. This definitely helped in
> > making the talk better.
> >
> > For those interested, there is a picture of myself giving the talk
> > with the beautiful Buildroot t-shirt (I wish I had a yellow helmet
> > to give the talk):
> >
> > ?http://www.flickr.com/photos/13825348 at N03/6303645373/in/photostream
>
> I would have loved the yellow helmet as well :-D
Idea to keep for a future talk I guess :)
> Thanks again for this talk, I think it was a great idea.
You're welcome!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-11-02 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 9:15 [Buildroot] Talk at Embedded Linux Conference Europe Thomas Petazzoni
2011-11-02 10:37 ` Thomas De Schampheleire
2011-11-02 12:28 ` Thomas Petazzoni [this message]
2011-11-07 13:26 ` Thomas Petazzoni
2011-11-07 13:39 ` Jonathan Dumaresq
2011-11-08 13:54 ` Mike Frysinger
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=20111102132849.5713060d@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