Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot at ELC: review/suggestions needed
Date: Thu, 14 Feb 2013 00:13:55 +0100	[thread overview]
Message-ID: <511C1E33.4060500@mind.be> (raw)
In-Reply-To: <201302132357.27593.yann.morin.1998@free.fr>

On 13/02/13 23:57, Yann E. MORIN wrote:
> Also, I wonder how and how much we could evaluate the Buildroot overhead.
> For example, considering a system that only has buildroot in it, how long
> does it take to build busybox, compile the filesystem generator (eg.
> genext2fs and fakeroot) and assemble the file system images, all manually
> (but only couting the build time, not the manual keying of the commands),
> and how long does it take Buildroot to achieve the same?

  You can approximate the overhead with 'make -qp > /dev/null'. 
Everything else that actually does get executed is necessary. Oh, wait: 
the time of dependencies.sh should also be taken along. But basically, 
the Buildroot overhead is roughly 5 seconds.

  Of course, with manually typing commands, you can make some shortcuts, 
like not using 'find' to find which things to remove in the finalize 
steps. On my allpackageyesconfig setup the finalize step takes in the 
order of 30 seconds.


  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-02-13 23:13 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
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 [this message]
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=511C1E33.4060500@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