Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Slides "Using Buildroot for real projects"
Date: Tue, 18 Oct 2011 23:35:07 +0200	[thread overview]
Message-ID: <201110182335.07799.arnout@mind.be> (raw)
In-Reply-To: <20111017184718.71afc290@skate>


On Monday 17 October 2011 18:47:18, Thomas Petazzoni wrote:
> 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.

 Of course, I can't stay behind with giving my comments!  They're a bit
broader than the earlier comments, though.

 For the 'What is Buildroot slide', I would split it in a 'What' and a 'Why' slide (bottom/top half).  Also, the goal for me is to build a complete Linux-based embedded system with the minimum amount of hassle.  That means:
 - minimal dependency on the build host's operating system (no specific bitbake or whatever package needs to be installed);
 - reproducible builds;
 - builds everything.

 About the "Buildroot can import external toolchains": it's not the option that I would advise at this time.  A major disadvantage is that there may be inconsistencies between what buildroot thinks the toolchain can do and what it actually can (unless it's a CodeSourcery toolchain, but those use glibc) - you have to define yourself what extra stuff the toolchain has.

 The board/<company>/<project>/linux-patches setup is exactly what I typically use as well.  I would like some future version of buildroot to simplify such a setup, i.e. you just configure board/<company>/<project> and buildroot looks for all the patches there.  But that's not for this presentation :-)

 One typical use case that is missing: in a company with several developers, you would put a download mirror in some central location and either point 
BR2_DL_DIR or BR2_PRIMARY_SITE to it.  (BTW, now I notice that the help text of BR2_PRIMARY_SITE incorrectly claims that it only works for AUTOTARGETS.)

 Another important hint: to debug, you should use output/host/usr/bin/<arch>-gdb -ex 'set solib-absolute-prefix output/staging'.

 And it may be worthwhile to talk about how you can contribute :-)  DCO, coding style, where to send it.


 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  31BB CF53 8660 6F88 345D  54CC A836 5879 20D7 CF43

  parent reply	other threads:[~2011-10-18 21:35 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
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 [this message]
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=201110182335.07799.arnout@mind.be \
    --to=arnout@mind.be \
    --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