From: Chris Larson <clarson@kergoth.com>
To: openembedded-devel@lists.openembedded.org
Cc: Chris Larson <chris_larson@mentor.com>
Subject: [PATCH 2/4] bitbake.conf: don't filter out nonexisting paths from FILESPATH
Date: Thu, 27 May 2010 14:16:26 -0700 [thread overview]
Message-ID: <1274994988-5750-2-git-send-email-clarson@kergoth.com> (raw)
In-Reply-To: <1274994988-5750-1-git-send-email-clarson@kergoth.com>
From: Chris Larson <chris_larson@mentor.com>
It's unnecessary, and can cause problems with amend.bbclass.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
diff --git a/conf/bitbake.conf b/conf/bitbake.conf
index ee93cd4..5dc6772 100644
--- a/conf/bitbake.conf
+++ b/conf/bitbake.conf
@@ -272,7 +272,7 @@ export MANIFEST = "${FILESDIR}/manifest"
FILE_DIRNAME = "${@os.path.dirname(bb.data.getVar('FILE', d))}"
FILESPATHBASE = "${FILE_DIRNAME}"
FILESPATHPKG = "${PF}:${P}:${PN}:${BP}:${BPN}:files:."
-FILESPATH = "${@':'.join([os.path.normpath(os.path.join(fp, p, o)) for fp in d.getVar('FILESPATHBASE', 1).split(':') for p in d.getVar('FILESPATHPKG', 1).split(':') for o in (d.getVar('OVERRIDES', 1) + ':').split(':') if os.path.exists(os.path.join(fp, p, o))])}"
+FILESPATH = "${@':'.join([os.path.normpath(os.path.join(fp, p, o)) for fp in d.getVar('FILESPATHBASE', 1).split(':') for p in d.getVar('FILESPATHPKG', 1).split(':') for o in (d.getVar('OVERRIDES', 1) + ':').split(':')])}"
FILESDIR = "${@bb.which(d.getVar('FILESPATH', 1), '.')}"
##################################################################
--
1.7.0.4
next prev parent reply other threads:[~2010-05-27 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 21:16 [PATCH 1/4] bitbake.conf: use := for BUILD_OS and BUILD_ARCH Chris Larson
2010-05-27 21:16 ` Chris Larson [this message]
2010-05-27 21:16 ` [PATCH 3/4] bitbake.conf: make the EXTENDPE bits slightly less disturbing Chris Larson
2010-05-27 21:16 ` [PATCH 4/4] bitbake.conf: Drop some unnecessary getVar usage in python snippets Chris Larson
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=1274994988-5750-2-git-send-email-clarson@kergoth.com \
--to=clarson@kergoth.com \
--cc=chris_larson@mentor.com \
--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