From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Fix: stage hidden files as well
Date: Mon, 26 Apr 2010 11:24:15 -0500 [thread overview]
Message-ID: <4BD5BE2F.7030407@mwester.net> (raw)
The following patch is a proposed patch to fix the problem where hidden
files are sometimes missed during staging. A specific example is that
the symbolic link ".config" is not copied to the kernel staging area,
which causes madwifi-ng to fail to build.
diff --git a/classes/staging.bbclass b/classes/staging.bbclass
index 32038a5..cb19cb9 100644
--- a/classes/staging.bbclass
+++ b/classes/staging.bbclass
@@ -35,6 +35,13 @@ sysroot_stage_dir() {
if [ -d "$src" ]; then
mkdir -p "$dest"
cp -fpPR "$src"/* "$dest"
+ # Get hidden files as well, but carefully
+ for i in "$src"/.*
+ do
+ if [ "$i" != "$src"/. -a "$i" != "$src"/.. ]; then
+ cp -fpPR "$i" "$dest"
+ fi
+ done
fi
}
If anyone has a better way to address the copy operations above, that
would be great.
-Mike (mwester)
next reply other threads:[~2010-04-26 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 16:24 Mike Westerhof [this message]
2010-04-28 21:49 ` Fix: stage hidden files as well Tom Rini
2010-04-28 23:52 ` Chris Larson
2010-04-29 7:05 ` Koen Kooi
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=4BD5BE2F.7030407@mwester.net \
--to=mike@mwester.net \
--cc=openembedded-devel@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