All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot at ELC: review/suggestions needed
Date: Mon, 11 Feb 2013 18:34:26 +0100	[thread overview]
Message-ID: <51192BA2.4040901@lucaceresoli.net> (raw)
In-Reply-To: <201302100047.23872.yann.morin.1998@free.fr>

Yann E. MORIN wrote:
> Thomas, All,
>
> On Saturday 09 February 2013 Thomas Petazzoni wrote:
>>   * Review the Buildroot poster I've made. The poster will be printed by
>>     the event organizers in big format, and I've tried to highlight the
>>     main fact about Buildroot, and recent developments.
>>     Seehttp://free-electrons.com/~thomas/pub/buildroot-poster.png
> I would add arrows to the lines, to further ensure that what is
> dark-green and brown is input to buildroot, while what is gray
> is the output.

To be precise, the toolchain can be either in input or an output toBR.
But I don't think it can be represented graphically in a nice and
understandable way...

About the poster: the official site is buildroot.net, not .org.

A few features that might not be obvious to a casual visitor and might be
interesting to put in the slideshow:
  - handles dependenciesautomatically;
  - does not require root permissions;
  - regular 3-months releases;
  - There is a comprehensive and maintained manual (have it handy in html
    and PDF!);
  - List some well-known supported boards (panda, sheevaplug, at91*,
    beaglebone...).

For the demo, I would keep ready a couple package's .mk files to show 
how one
can easily add a package. IMHO the simplicity in adding packages is the
number 1 BR feature for a beginner.
I suggest to show one of the simplest available, that does need any tweak
(e.g. sdparm, 6 non-empty lines, 0 patches!) and a moderately complex one
(maybe logrotate, grep, libpng?).

Luca

  parent reply	other threads:[~2013-02-11 17:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 18:57 [Buildroot] Buildroot at ELC: review/suggestions needed Thomas Petazzoni
2013-02-09 19:06 ` Thomas Petazzoni
2013-02-09 23:47 ` Yann E. MORIN
2013-02-10  9:50   ` Peter Korsgaard
2013-02-10 10:59     ` Yann E. MORIN
2013-02-11  8:24   ` Thomas Petazzoni
2013-02-11  9:51     ` Will Newton
2013-02-11 10:31       ` Thomas Petazzoni
2013-02-11 17:34   ` Luca Ceresoli [this message]
2013-02-10 11:28 ` Stephan Hoffmann
2013-02-11  8:26   ` Thomas Petazzoni
2013-02-10 12:46 ` Belisko Marek
2013-02-11  8:42   ` Thomas Petazzoni
2013-02-11  8:33 ` Yegor Yefremov
2013-02-11 13:38 ` Shawn J. Goff
2013-02-24  4:07   ` Thomas Petazzoni
2013-02-13 22:13 ` Thomas Petazzoni
2013-02-13 22:57   ` Yann E. MORIN
2013-02-13 23:13     ` Arnout Vandecappelle
2013-02-14  5:35   ` Baruch Siach
2013-02-14  9:46   ` Thomas Petazzoni
2013-02-14  9:54     ` Jeremy Rosen
2013-02-14  9:58       ` Thomas Petazzoni
2013-02-14 12:34     ` Baruch Siach
2013-02-14  9:53   ` Will Moore
2013-02-14 10:05     ` 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=51192BA2.4040901@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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.