From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Steffen Sledz <sledz@dresearch-fe.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: inc and bb vs. layers
Date: Tue, 09 Oct 2012 14:18:21 +0100 [thread overview]
Message-ID: <2358307.KjMcZMityv@helios> (raw)
In-Reply-To: <507422A9.9040505@dresearch-fe.de>
On Tuesday 09 October 2012 15:12:09 Steffen Sledz wrote:
> Given to files
>
> foo.inc
> foo.bb (which requires foo.inc)
>
> in layer Foo. Now i want to write a new
>
> bar.bb (which requires foo.inc too)
>
> in layer Bar. Is this possible without keeping a copy of foo.inc in Bar?
Certainly, you just need to specify the path from the base of the layer where
the inc file resides in your "require" statement, for example:
require recipes-graphics/xorg-app/xorg-app-common.inc
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-10-09 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 13:12 inc and bb vs. layers Steffen Sledz
2012-10-09 13:18 ` Paul Eggleton [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=2358307.KjMcZMityv@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sledz@dresearch-fe.de \
/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