From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Request for review: buildroot in Open Mobile Linux devroom of FOSDEM
Date: Thu, 26 Jan 2012 16:38:12 +0100 [thread overview]
Message-ID: <20120126163812.02917ef3@skate> (raw)
In-Reply-To: <201201160950.18702.arnout@mind.be>
Le Mon, 16 Jan 2012 09:50:18 +0100,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> As I announced earlier, I'll be giving a talk in the Open Mobile
> Linux devroom on FOSDEM. I would like to get feedback on the
> slides. You can find them on http://mind.be/?page=publications
> (in .odp and .pdf).
>
> It's a 15 minute talk. My goal is not to explain how to use
> buildroot, but rather to convince the audience that buildroot (or
> something similar) is the way to go for "open" embedded devices,
> because it empowers the user to make modifications and improvements.
>
> My slides aren't really stand-alone, so it may actually be difficult
> to review them without hearing my talk :-(
I did a quick review, and those slides look good. As you say, without
the actual speech, it's hard to see where you want to go. From my point
of view, the very important thing with embedded Linux build systems is
repeatability/reproducibility. I have seen way too many
people/companies building their embedded Linux system by randomly
cross-compiling dozens of libraries manually, without any way of
reproducing that build process.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-01-26 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 8:50 [Buildroot] Request for review: buildroot in Open Mobile Linux devroom of FOSDEM Arnout Vandecappelle
2012-01-16 9:00 ` Baruch Siach
2012-01-16 9:13 ` Arnout Vandecappelle
2012-01-26 15:38 ` Thomas Petazzoni [this message]
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=20120126163812.02917ef3@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