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 presentation at Embedded Linux Conference 2009
Date: Fri, 20 Mar 2009 10:37:51 +0100	[thread overview]
Message-ID: <20090320103751.3652df54@surf> (raw)

Hi,

Even though I'm by far not the most active developer of Buildroot, I
thought that the recent revival of the project was an interesting
opportunity to promote the project. So, I've submitted a presentation
for the Embedded Linux Conference [1], that will be held from April, 6th to
April, 8th in San Francisco, US and this presentation has been accepted
[2].

I will both present why systems like Buildroot are necessary
(cross-compilation is painful, sharing recipes is nice, and having an
automated and reproducible build systems is a must) and then how
Buildroot fill these needs, how it works and how it can be extended.

I'll try to share my slides prior to the conference so that the
Buildroot community can help in improving the presentation so that the
project will be promoted as best as possible.

Sincerly,

Thomas

[1] http://www.embeddedlinuxconference.com/elc_2009/index.html
[2] http://www.embeddedlinuxconference.com/elc_2009/sessions.html#Petazzoni
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

             reply	other threads:[~2009-03-20  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20  9:37 Thomas Petazzoni [this message]
2009-03-20 10:20 ` [Buildroot] Buildroot presentation at Embedded Linux Conference 2009 Peter Korsgaard
2009-03-25 16:46   ` Thomas Petazzoni
2009-03-25 18:23     ` Thiago A. Corrêa
2009-03-25 18:46     ` Steve Calfee

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=20090320103751.3652df54@surf \
    --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