From: Joshua Lock <josh@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-core] requires on own .bb file
Date: Mon, 16 Apr 2012 09:27:48 -0700 [thread overview]
Message-ID: <4F8C4884.3040207@linux.intel.com> (raw)
In-Reply-To: <CAOHjBZt=6w7D8jzj7bOe+kMAZ8oFEBThge3dopK10mFDenFbAQ@mail.gmail.com>
On 16/04/12 01:42, Giuseppe Condorelli wrote:
> Hi all,
>
> I wrote a personal .bb file and added it on the meta-<myproject> tree.
> This .bb file requires a .inc file already available in the native oe-core
> meta directory.
> How can I include it into my .bb file? If I add "require<blablabla>.inc"
> it fails because it
> is not able to found the given .inc file. In other words I need to copy it
> into the meta-<myproject> tree.
The require line should be a path relative to a BBPATH entry.
For e.g. if I wanted to use the dbus.inc I would:
require recipes-core/dbus/dbus.inc
Cheers,
Joshua
--
Joshua Lock
Yocto Project
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-04-16 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 8:42 [oe-core] requires on own .bb file Giuseppe Condorelli
2012-04-16 16:27 ` Joshua Lock [this message]
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=4F8C4884.3040207@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox