From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH] staging: Use hardlinking for sysroot_stage_dir
Date: Wed, 13 Nov 2013 18:05:30 +0000 [thread overview]
Message-ID: <1384365930.6460.99.camel@ted> (raw)
This saves about 2GB on a core-image-sato build so is worth doing and is
consistent with our efforts to try and decrease our build footprint.
Build time in my local test seemed unaffected but on more IO bound
machines it should help.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass
index ddba0c9..94abcda 100644
--- a/meta/classes/staging.bbclass
+++ b/meta/classes/staging.bbclass
@@ -7,14 +7,11 @@ sysroot_stage_dir() {
return
fi
- # We only want to stage the contents of $src if it's non-empty so first rmdir $src
- # then if it still exists (rmdir on non-empty dir fails) we can copy its contents
- rmdir "$src" 2> /dev/null || true
- # However we always want to stage a $src itself, even if it's empty
mkdir -p "$dest"
- if [ -d "$src" ]; then
- tar -cf - -C "$src" -p . | tar -xf - -C "$dest"
- fi
+ (
+ cd $src
+ find . -print0 | cpio --null -pdlu $dest
+ )
}
sysroot_stage_stripdir() {
reply other threads:[~2013-11-13 18:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1384365930.6460.99.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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