From: Gary Thomas <gary@mlbassoc.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: New warning
Date: Wed, 20 Jun 2012 16:51:20 -0600 [thread overview]
Message-ID: <4FE253E8.7090901@mlbassoc.com> (raw)
In-Reply-To: <CAMKF1so1L3GNuELFb4stPPORTwN29vOLngJM_x_9BrV7_jMaiQ@mail.gmail.com>
On 2012-06-20 15:55, Khem Raj wrote:
> On Wed, Jun 20, 2012 at 12:12 PM, Gary Thomas<gary@mlbassoc.com> wrote:
>> This happens when I have two intertwined layers - I have a recipe in layer1
>> which references a file satisfied only by layer2.
>
> why not move the reference from layer1 to layer2 as well ?
Layer1 holds the recipe and I find it more informative to have the
reference there - that way the .bbappends in layer2 _must_ define
it and the dependency is obvious since the recipe will fail without
this file being specified.
My use case is layer1 has a generic kernel recipe and layer2 (BSP)
has a platform specific patch for that kernel. I have other use
cases, but this is indicative of how I view the layering.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-06-20 22:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 19:12 New warning Gary Thomas
2012-06-20 21:55 ` Khem Raj
2012-06-20 22:51 ` Gary Thomas [this message]
2012-06-21 8:26 ` Andrea Adami
2012-06-22 9:44 ` Paul Eggleton
2012-06-22 11:49 ` Gary Thomas
2012-06-22 12:35 ` Tomas Frydrych
2012-06-22 13:01 ` Paul Eggleton
2012-06-22 13:05 ` Paul Eggleton
2012-06-22 13:31 ` Gary Thomas
2012-06-22 14:25 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2012-10-02 15:34 Gary Thomas
2012-10-02 15:43 ` Richard Purdie
2012-10-03 6:22 ` Khem Raj
2016-06-08 2:55 Gary Thomas
2016-06-08 3:20 ` Christopher Larson
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=4FE253E8.7090901@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.com \
/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.