* Weird FILESPATH issue
@ 2013-04-05 12:53 Gary Thomas
2013-04-05 17:04 ` Gary Thomas
0 siblings, 1 reply; 5+ messages in thread
From: Gary Thomas @ 2013-04-05 12:53 UTC (permalink / raw)
To: Yocto Project
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
------------------------------------------------------------
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Weird FILESPATH issue
2013-04-05 12:53 Weird FILESPATH issue Gary Thomas
@ 2013-04-05 17:04 ` Gary Thomas
2013-04-05 17:31 ` Paul Eggleton
0 siblings, 1 reply; 5+ messages in thread
From: Gary Thomas @ 2013-04-05 17:04 UTC (permalink / raw)
To: Yocto Project
On 2013-04-05 06:53, Gary Thomas wrote:
> 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?
>
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 :-(
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Weird FILESPATH issue
2013-04-05 17:04 ` Gary Thomas
@ 2013-04-05 17:31 ` Paul Eggleton
2013-04-05 23:41 ` Gary Thomas
0 siblings, 1 reply; 5+ messages in thread
From: Paul Eggleton @ 2013-04-05 17:31 UTC (permalink / raw)
To: Gary Thomas; +Cc: yocto
On Friday 05 April 2013 11:04:15 Gary Thomas wrote:
> On 2013-04-05 06:53, Gary Thomas wrote:
> > 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 :-(
The FILESPATH line you referred to is very old and probably no longer
necessary. Try dropping it and see if everything works.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Weird FILESPATH issue
2013-04-05 17:31 ` Paul Eggleton
@ 2013-04-05 23:41 ` Gary Thomas
2013-04-06 12:01 ` Gary Thomas
0 siblings, 1 reply; 5+ messages in thread
From: Gary Thomas @ 2013-04-05 23:41 UTC (permalink / raw)
To: Paul Eggleton; +Cc: yocto
On 2013-04-05 11:31, Paul Eggleton wrote:
> On Friday 05 April 2013 11:04:15 Gary Thomas wrote:
>> On 2013-04-05 06:53, Gary Thomas wrote:
>>> 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 :-(
>
> 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.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Weird FILESPATH issue
2013-04-05 23:41 ` Gary Thomas
@ 2013-04-06 12:01 ` Gary Thomas
0 siblings, 0 replies; 5+ messages in thread
From: Gary Thomas @ 2013-04-06 12:01 UTC (permalink / raw)
To: yocto
On 2013-04-05 17:41, Gary Thomas wrote:
> On 2013-04-05 11:31, Paul Eggleton wrote:
>> On Friday 05 April 2013 11:04:15 Gary Thomas wrote:
>>> On 2013-04-05 06:53, Gary Thomas wrote:
>>>> 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 :-(
>>
>> 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.
>
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.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-04-06 12:01 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-05 12:53 Weird FILESPATH issue Gary Thomas
2013-04-05 17:04 ` Gary Thomas
2013-04-05 17:31 ` Paul Eggleton
2013-04-05 23:41 ` Gary Thomas
2013-04-06 12:01 ` Gary Thomas
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.