Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Slides "Using Buildroot for real projects"
Date: Mon, 17 Oct 2011 23:13:46 +0200	[thread overview]
Message-ID: <87hb3748z9.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20111017184718.71afc290@skate> (Thomas Petazzoni's message of "Mon, 17 Oct 2011 18:47:18 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Hello,
 Thomas> At ELCE, I will be talking about "Using Buildroot for real projects".
 Thomas> You can see my talk summary at
 Thomas> https://events.linuxfoundation.org/events/embedded-linux-conference-europe/petazzoni.

 Thomas> The current (unfinished) status of my slides is visible at:
 Thomas>   http://free-electrons.com/~thomas/pub/using-buildroot-real-project.pdf

Thanks, a few quick comments:

p3: s/How it works?/How does it work?/
p5: minor, configuration doesn't match output on p6
p7: "It does not track which packages installs what" <- Is that
    important to know how it works?
p9: use uclibc and rootfs size would be half ;)
p11: s/needs to build rebuilt/needs to be rebuilt/
p11: s/built with crosstool-NG/from above/
p12: s/knows some/contains presets for/
p12: s/well-known toolchains/well-known binary toolchains/
p14: s/for it build/for it to build/
p16: "Up to Buildroot 2011.11" reads a bit odd to me (E.G. is it now
     fixed or not?) Perhaps simply say "Until recently, it wasn't easy
     to use Buildroot with a custom"

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-10-17 21:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 16:47 [Buildroot] [RFC] Slides "Using Buildroot for real projects" Thomas Petazzoni
2011-10-17 21:13 ` Peter Korsgaard [this message]
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=87hb3748z9.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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