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] "Buildroot: what's new" slides
Date: Fri, 27 Oct 2017 14:54:02 +0200	[thread overview]
Message-ID: <20171027145402.2404fa4b@windsurf.lan> (raw)

Hello,

On Tuesday this week, I gave a talk "Buildroot: what's new?" at the
Embedded Linux Conference Europe in Prague. I have published the slides
online at
http://free-electrons.com/pub/conferences/2017/elce/petazzoni-buildroot-whats-new/petazzoni-buildroot-whats-new.pdf.

The room was rather full, I believe perhaps 60-80 people in the
audience, but the projectors were so bright that I couldn't really see,
so perhaps Arnout, Peter or Yann who were in the audience can give
more details.

The talk included a poll. I think about 90% of the room already knew
about Buildroot, and a good 60-70% of the room was already using
Buildroot. Perhaps 30-40% of the room was using OE/Yocto, and less than
10% was using OpenWRT. Note that this is of course not representative
of the build system "market share" since people showing up at a
Buildroot talk are likely to already be interested in this build system
more than in others.

This time around, my talk nicely fit within the time slot, so there has
been some time for questions. The ones that I remember:

 - Is there some support for the Rust language. I mentioned the patches
   from Eric Le Bihan, and said help was definitely welcome.

 - A person asked about syslinux support on the target: we currently
   build syslinux itself for the target, but the tools are built for
   the host, but there are scenarios where the tools are needed on the
   target as well. I had the chance to discuss after the talk with this
   person from Airbus, and I explained how it should probably be done
   (host-syslinux installing the host tools, target syslinux installing
   syslinux itself with an option for the target tools)

 - A person asked how to use Buildroot during application development,
   so I gave some more details about <pkg>_OVERRIDE_SRCDIR and how it's
   intended to work.

Perhaps Arnout, Peter or Yann will remember other questions.

All in all, I think it was a good experience, large audience,
interesting questions and feedback. It is worth mentioning that Yann
gave a Buildroot related talk right after mine, I'm sure he will be
publishing his slides very soon.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

             reply	other threads:[~2017-10-27 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 12:54 Thomas Petazzoni [this message]
2017-10-28 14:36 ` [Buildroot] "Buildroot: what's new" slides Yann E. MORIN
2017-10-28 14:53   ` Thomas Petazzoni
2017-10-28 15:00     ` Yann E. MORIN
2017-10-30 15:29     ` Marcus Hoffmann
2017-10-29 12:43 ` Eric Le Bihan

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=20171027145402.2404fa4b@windsurf.lan \
    --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