All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel@lists.openembedded.org
Cc: Chris Larson <clarson@kergoth.com>
Subject: Re: understanding overlays
Date: Thu, 28 Jul 2011 07:48:43 +0200	[thread overview]
Message-ID: <4E30F83B.3080907@dresearch-fe.de> (raw)
In-Reply-To: <CABcZANnYw1Njsi=8BUr0=Mf-O78VEXF9XJQy5-Oqm66+=A7nQQ@mail.gmail.com>

On 27.07.2011 18:12, Chris Larson wrote:
> On Wed, Jul 27, 2011 at 7:24 AM, Steffen Sledz <sledz@dresearch-fe.de> wrote:
>> I'm not really familiar with the oe/bitbake overlay details. So please forgive me if this is a faq. ;-)
>>
>> Is the overlay package or file based?
>>
>> Or in other words is the following scenario possible?
>>
>> base layer:
>>
>>  recipes/
>>    foo/
>>      foo.inc
>>      foo_x.y.z.bb
>>
>> overlay:
>>
>>  recipes/
>>    foo/
>>      foo.inc
>>
>> And than build foo-x.y.z with the foo.inc from the overlay.
> 
> That depends. If the .bb does 'require foo.inc', then no, it will use
> the local one. If it does 'require recipes/foo/foo.inc', then yes, it
> will use the overlay one, assuming the overlay is before the main
> layer in your BBLAYERS.

Thx. What about files referenced e.g. in SRC_URI? I assume that always the ones from the 'highest' layer are used. Right?

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058



  reply	other threads:[~2011-07-28  5:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 14:24 understanding overlays Steffen Sledz
2011-07-27 16:12 ` Chris Larson
2011-07-28  5:48   ` Steffen Sledz [this message]
2011-07-30 17:07     ` Khem Raj

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=4E30F83B.3080907@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=clarson@kergoth.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 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.