From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: require *.bbappend
Date: Mon, 19 Dec 2011 10:25:29 -0800 [thread overview]
Message-ID: <4EEF8199.9090007@linux.intel.com> (raw)
In-Reply-To: <201112170258.10212.schnitzeltony@gmx.de>
On 16/12/11 17:58, Andreas Müller wrote:
> Hi
>
> I have the following use case:
>
> In my working layer I would like to have a recipe adding functionality to a
> recipe from another layer (e.g systemd-image.bb from angstrom) with a different
> name ( -> no bbappend ). How about
>
> * create systemd-image.bbapend with just 'FILESEXTRAPATHS := "${THISDIR}"' to
> get it into the scope of my layer
> * create a recipe which contains 'require systemd-image.bbappend'
>
> Currently parser complains that systemd-image.bbappend is not a BitBake file.
I think this should work and the issue you're seeing is that require
wants a relative PATH from BBPATH.
i.e. require recipes-images/angstrom/systemd-image.bb
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-19 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 1:58 require *.bbappend Andreas Müller
2011-12-19 18:25 ` Joshua Lock [this message]
2011-12-19 22:05 ` Andreas Müller
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=4EEF8199.9090007@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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.