Weird FILESPATH issue
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?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 17 lines · Gary Thomas
I'm trying to write a patch for this recipe:
meta/recipes-devtools/python/python-pygobject_2.27.91.bbI 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
Quoted 9 lines
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?
What I don't get is that I've done this exact same style of .bbappend for other recipes and it works fine. For example, I have this
${LAYER}/recipes-sato/gtk-engines/gtk-sato-engine_git.bbappend:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI_append = " file://adjust-sato-theme.patch "
PACKAGE_ARCH = "${MACHINE_ARCH}"This .bbappend file works perfectly :-(
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 14 lines · On Friday 05 April 2013 11:04:15 Gary Thomas wrote:
Quoted 9 lines · Gary Thomas
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?
What I don't get is that I've done this exact same style of .bbappend for other recipes and it works fine. For example, I have this
Quoted 6 lines
${LAYER}/recipes-sato/gtk-engines/gtk-sato-engine_git.bbappend: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" SRC_URI_append = " file://adjust-sato-theme.patch " PACKAGE_ARCH = "${MACHINE_ARCH}"This .bbappend file works perfectly :-(
The FILESPATH line you referred to is very old and probably no longer necessary. Try dropping it and see if everything works.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 20 lines · Paul Eggleton
Quoted 19 lines · On Friday 05 April 2013 11:04:15 Gary Thomas wrote:
Quoted 9 lines · Gary Thomas
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?
What I don't get is that I've done this exact same style of .bbappend for other recipes and it works fine. For example, I have this
${LAYER}/recipes-sato/gtk-engines/gtk-sato-engine_git.bbappend: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" SRC_URI_append = " file://adjust-sato-theme.patch " PACKAGE_ARCH = "${MACHINE_ARCH}"
Quoted 4 lines
Quoted 1 line
This .bbappend file works perfectly :-(
The FILESPATH line you referred to is very old and probably no longer necessary. Try dropping it and see if everything works.
I did and it still doesn't work. Now it looks at many more directories, including the overrides, etc, but still not looking in the layer that contains the .bbappend. I now get these:
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/i686
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/cobra4430p82
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/omap4
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/armv7a
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/amltd
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/i686
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/cobra4430p82
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/omap4
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/armv7a
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/amltd
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/i686
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/cobra4430p82
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/omap4
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/armv7a
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/amltd
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/i686
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/cobra4430p82
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/omap4
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/armv7a
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/amltd
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/
/home/local/poky-multi/meta/recipes-devtools/python/files/i686
/home/local/poky-multi/meta/recipes-devtools/python/files/cobra4430p82
/home/local/poky-multi/meta/recipes-devtools/python/files/omap4
/home/local/poky-multi/meta/recipes-devtools/python/files/armv7a
/home/local/poky-multi/meta/recipes-devtools/python/files/amltd
/home/local/poky-multi/meta/recipes-devtools/python/files/Still very confused.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 60 lines · Gary Thomas
Quoted 20 lines · Paul Eggleton
Quoted 19 lines · On Friday 05 April 2013 11:04:15 Gary Thomas wrote:
Quoted 9 lines · Gary Thomas
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?
What I don't get is that I've done this exact same style of .bbappend for other recipes and it works fine. For example, I have this
${LAYER}/recipes-sato/gtk-engines/gtk-sato-engine_git.bbappend: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" SRC_URI_append = " file://adjust-sato-theme.patch " PACKAGE_ARCH = "${MACHINE_ARCH}"Quoted 4 lines
Quoted 1 line
This .bbappend file works perfectly :-(
The FILESPATH line you referred to is very old and probably no longer necessary. Try dropping it and see if everything works.
I did and it still doesn't work. Now it looks at many more directories, including the overrides, etc, but still not looking in the layer that contains the .bbappend. I now get these:
/home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/i686 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/cobra4430p82 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/omap4 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/armv7a /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/amltd /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native-2.27.91/ /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/i686 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/cobra4430p82 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/omap4 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/armv7a /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/amltd /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-native/ /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/i686 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/cobra4430p82 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/omap4 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/armv7a /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/amltd /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject-2.27.91/ /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/i686 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/cobra4430p82 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/omap4 /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/armv7a /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/amltd /home/local/poky-multi/meta/recipes-devtools/python/python-pygobject/ /home/local/poky-multi/meta/recipes-devtools/python/files/i686 /home/local/poky-multi/meta/recipes-devtools/python/files/cobra4430p82 /home/local/poky-multi/meta/recipes-devtools/python/files/omap4 /home/local/poky-multi/meta/recipes-devtools/python/files/armv7a /home/local/poky-multi/meta/recipes-devtools/python/files/amltd /home/local/poky-multi/meta/recipes-devtools/python/files/
Quoted 2 lines
Still very confused.
I figured it out - there were compounding problems here.
Firstly, the FILESPATH setting in the main recipe is wrong and needs to be removed. Secondly, my .bbappend override needs to be written using ':=' like this:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:${THISDIR}/${PN}:"
Now it's working fine.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------