From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: saul.wold@intel.com
Subject: [PATCH V2 0/1] insane: add checking to standardize how .bbappend files do FILESEXTRAPATHS
Date: Mon, 21 Jul 2014 14:17:33 +0800 [thread overview]
Message-ID: <cover.1405923190.git.hongxu.jia@windriver.com> (raw)
Change in V2:
- It is more reasonable to move the checking to insance.bbclass
rather than create a new bbclass.
Test Steps:
1) Edit meta-yocto/recipes-core/busybox/busybox_%.bbappend
and assigned FILESEXTRAPATHS incorrectly:
...
--- a/meta-yocto/recipes-core/busybox/busybox_%.bbappend
+++ b/meta-yocto/recipes-core/busybox/busybox_%.bbappend
@@ -1,2 +1,2 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:"
+FILESEXTRAPATHS := "${THISDIR}/${BPN}:"
...
2) bitbake busybox
...
ERROR: FILESEXTRAPATHS-variable, must always use _prepend (or _append)
type of assignment. Please assign it with the format of:
FILESEXTRAPATHS_append := ${THISDIR}/Your_Files_Path or
FILESEXTRAPATHS_prepend := ${THISDIR}/Your_Files_Path
in your bbappend file
ERROR: Failed to parse recipe: /home/jiahongxu/yocto/poky/meta/recipes-core/busybox/busybox_git.bb
...
//Hongxu
The following changes since commit 4d2ac6f6df2b3ef98699dd4f7afadb2d994222bb:
rootfs: Remove the extraneous install directory (2014-07-19 00:18:21 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/filesextrapaths
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/filesextrapaths
Hongxu Jia (1):
insane: add checking to standardize how .bbappend files do
FILESEXTRAPATHS
meta/classes/insane.bbclass | 10 ++++++++++
meta/classes/utils.bbclass | 2 ++
meta/conf/bitbake.conf | 2 ++
3 files changed, 14 insertions(+)
--
1.8.1.2
next reply other threads:[~2014-07-21 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 6:17 Hongxu Jia [this message]
2014-07-21 6:17 ` [PATCH 1/1] insane: add checking to standardize how .bbappend files do FILESEXTRAPATHS Hongxu Jia
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=cover.1405923190.git.hongxu.jia@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
/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