From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Weird FILESPATH issue
Date: Fri, 05 Apr 2013 06:53:07 -0600 [thread overview]
Message-ID: <515EC933.70305@mlbassoc.com> (raw)
I'm trying to write a patch for this recipe:
meta/recipes-devtools/python/python-pygobject_2.27.91.bb
I tried with a .bbappend that looks like this:
FILESEXTRAPATHS_append = ":${THISDIR}/${PN}-${PV}:${THISDIR}/${PN}"
SRC_URI_append = " file://fix-registration-warnings.patch "
Also like this:
FILESPATH_append = ":${THISDIR}/${BPN}-${PV}"
SRC_URI_append = " file://fix-registration-warnings.patch "
to which I get this error:
ERROR: Fetcher failure: Unable to find file file://fix-registration-warnings.patch anywhere. The paths that were searched were:
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject
/home/local/poky-multi/meta/recipes-devtools/python/files
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91
/home/local/p82_soft/downloads
I think the problem is because the main recipe contains this line:
FILESPATH = "${FILE_DIRNAME}/python-pygobject:${FILE_DIRNAME}/files"
How can I write my .bbappend file to pick up the patch from my [local] layer?
Thanks
n.b. isn't that 'FILESPATH' line in the main recipe rather unfriendly?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2013-04-05 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 12:53 Gary Thomas [this message]
2013-04-05 17:04 ` Weird FILESPATH issue Gary Thomas
2013-04-05 17:31 ` Paul Eggleton
2013-04-05 23:41 ` Gary Thomas
2013-04-06 12:01 ` Gary Thomas
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=515EC933.70305@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.