From: <colin.helliwell@ln-systems.com>
To: <yocto@yoctoproject.org>
Subject: Unpack hierarchy - jethro vs. krogoth
Date: Tue, 28 Mar 2017 11:33:53 +0100 [thread overview]
Message-ID: <1ee401d2a7ae$cc2fabb0$648f0310$@ln-systems.com> (raw)
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...!
next reply other threads:[~2017-03-28 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 10:33 colin.helliwell [this message]
2017-03-28 14:59 ` Unpack hierarchy - jethro vs. krogoth Colin Helliwell
2017-03-28 23:05 ` Andre McCurdy
2017-03-29 8:43 ` Colin Helliwell
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='1ee401d2a7ae$cc2fabb0$648f0310$@ln-systems.com' \
--to=colin.helliwell@ln-systems.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.