[yocto] Unpack hierarchy - jethro vs. krogoth

[Andre McCurdy]

On Tue, Mar 28, 2017 at 3:33 AM,  <colin.helliwell at ln-systems.com> wrote:
> Is there a change to recipe parsing and/or variables between jethro and
> krogoth?
> I'm migrating from the former to the latter and have hit a patch failure.
> Looking at the unpacked source, jethro has the relevant file at
>     build/tmp/work/XXX-poky-linux-gnueabi/linmux/3.0.2-r0/driver/
> whereas krogoth has it at
>     build/tmp/work/XXX-poky-linux-gnueabi/linmux/3.0.2-r0/driver/driver/
>
> Indeed, all the sources have been unpacked under an additional 'driver'
> directory level .e.g.
>     src/driver/*  ->  3.0.2-r0/driver/driver/
>     src/config/*  ->  3.0.2-r0/driver/config/
> instead of
>     src/driver/*  ->  3.0.2-r0/driver/
>     src/config/*  ->  3.0.2-r0/config/
>
>
> The recipe includes
> SRC_URI = "file://driver/*.c \
>            file://driver/*.h \
>            file://Makefile \
>            file://COPYING \
>           "
> FILESEXTRAPATHS_prepend := "${BSPDIR}/../Apps/MyDriver/src:"
> S = "${WORKDIR}"
>
> As I say, it works on jethro...!

There were some changes in bitbake's handling of file:// SRC_URI entries:

  http://git.openembedded.org/bitbake/commit/?id=e659a3b0c2771679057ee3e13cd42e6c62383ff2

Is the behaviour more consistent if you remove one of the
"file://driver/*.[ch]" entries from SRC_URI? Or if you replace both
with a single entry to copy entire driver directory (ie
"file://driver") and avoid using wildcards?

> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto