All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Weird FILESPATH issue
Date: Fri, 05 Apr 2013 17:41:48 -0600	[thread overview]
Message-ID: <515F613C.6080909@mlbassoc.com> (raw)
In-Reply-To: <30341079.23PBRlhEQk@helios>

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
------------------------------------------------------------


  reply	other threads:[~2013-04-05 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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=515F613C.6080909@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=paul.eggleton@linux.intel.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.