From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Slides "Using Buildroot for real projects"
Date: Mon, 17 Oct 2011 18:47:18 +0200 [thread overview]
Message-ID: <20111017184718.71afc290@skate> (raw)
Hello,
At ELCE, I will be talking about "Using Buildroot for real projects".
You can see my talk summary at
https://events.linuxfoundation.org/events/embedded-linux-conference-europe/petazzoni.
The current (unfinished) status of my slides is visible at:
http://free-electrons.com/~thomas/pub/using-buildroot-real-project.pdf
The goal of the talk is to give some recommendations and best practices
on how to use Buildroot. As I'm sure I forgot a lot of things in my
slides above, I'd like to know what you, Buildroot developers/users,
would have to say on the topic, so that I can improve the contents of
this presentation.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2011-10-17 16:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 16:47 Thomas Petazzoni [this message]
2011-10-17 21:13 ` [Buildroot] [RFC] Slides "Using Buildroot for real projects" Peter Korsgaard
2011-10-18 7:26 ` Baruch Siach
2011-10-21 13:44 ` Thomas Petazzoni
2011-10-18 9:22 ` Thomas De Schampheleire
2011-10-18 21:35 ` Arnout Vandecappelle
2011-10-19 6:29 ` Thomas De Schampheleire
2011-10-21 13:43 ` Thomas Petazzoni
2011-10-21 13:51 ` Yegor Yefremov
2011-10-21 13:58 ` Thomas Petazzoni
2011-10-21 14:24 ` Yegor Yefremov
2011-10-21 15:34 ` Thomas Petazzoni
2011-10-21 14:33 ` Will Wagner
2011-10-21 15:25 ` Thomas Petazzoni
2011-10-22 17:04 ` Thomas De Schampheleire
2011-10-23 12:37 ` Baruch Siach
2011-10-24 15:32 ` Thomas Petazzoni
2011-10-24 16:42 ` Yann E. MORIN
2011-10-24 17:17 ` Thomas Petazzoni
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=20111017184718.71afc290@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.