From: Sam Ravnborg <sam@ravnborg.org>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/4] build: minimize rebuilds
Date: Tue, 26 Dec 2017 19:32:36 +0100 [thread overview]
Message-ID: <20171226183236.GA26708@ravnborg.org> (raw)
Following patchset minimizes re-builds.
With the setup I use at the moment where I run
build tests on 100+ arm related boards I see that the
build time is reduced to half - for an otherwise
clean build with no changes.
In other words - the wall clock time for a
simple "try to build all boards" where nothing
has changed goes from ~2:35 minutes to 1:21 minutes
The patches has been tested in my local setup - and
no missing rebuilds was seen.
Sam Ravnborg (4):
build: fix that defaultenv is always rebuilt
build: fix that passwd.h is always built
build: fix that the bbenv file is always rebuilt
build: fix that LZO file is always rebuilt
common/Makefile | 28 +++++++++++++++-------------
defaultenv/Makefile | 4 ++--
scripts/Kbuild.include | 12 +++++++-----
scripts/Makefile.lib | 2 +-
4 files changed, 25 insertions(+), 21 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-12-26 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 18:32 Sam Ravnborg [this message]
2017-12-26 18:35 ` [PATCH 1/4] build: fix that defaultenv is always rebuilt Sam Ravnborg
2017-12-26 18:36 ` [PATCH 2/4] build: fix that passwd.h is always built Sam Ravnborg
2017-12-26 18:36 ` [PATCH 3/4] build: fix that the bbenv file is always rebuilt Sam Ravnborg
2017-12-26 18:36 ` [PATCH 4/4] build: fix that LZO " Sam Ravnborg
2018-01-05 10:49 ` Sascha Hauer
2018-01-05 14:57 ` Sascha Hauer
2018-01-06 7:34 ` Sam Ravnborg
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=20171226183236.GA26708@ravnborg.org \
--to=sam@ravnborg.org \
--cc=barebox@lists.infradead.org \
/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