From: Patrick Ohly <patrick.ohly@intel.com>
To: Takashi Matsuzawa <tmatsuzawa@xevo.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: dynamic-layers?
Date: Fri, 26 May 2017 15:51:57 +0200 [thread overview]
Message-ID: <1495806717.16923.120.camel@intel.com> (raw)
In-Reply-To: <DM5PR0101MB2953F385C585BBDE4E224896B6FC0@DM5PR0101MB2953.prod.exchangelabs.com>
On Fri, 2017-05-26 at 08:09 +0000, Takashi Matsuzawa wrote:
> Hello.
>
>
> So, this is the case I have to be careful about the order of conf
> files listed in BBLAYERS list?
>
> i.e. if I have dynamic-layers line in my layer X and expansion need to
> take care of layer A, B, C, then, A, B, C needs to be apper before X
> within BBLAYERS list.
Yes, I think that's how it is meant to be used.
The reason is that layers get added one-by-one in the order in which
they appear in BBLAYERS, and then the code in
meta-freescale/conf/layer.conf only sees what has been added already.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-05-26 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 10:30 dynamic-layers? Takashi Matsuzawa
2017-05-24 14:19 ` dynamic-layers? Gary Thomas
2017-05-24 14:19 ` dynamic-layers? Nicolas Dechesne
2017-05-25 1:03 ` dynamic-layers? Takashi Matsuzawa
2017-05-25 6:26 ` dynamic-layers? Takashi Matsuzawa
2017-05-25 14:12 ` Fw: [yocto] dynamic-layers? Takashi Matsuzawa
2017-06-19 14:51 ` Otavio Salvador
2017-06-19 15:18 ` Takashi Matsuzawa
2017-06-19 17:58 ` Otavio Salvador
2017-06-28 2:41 ` Takashi Matsuzawa
2017-06-28 14:23 ` Otavio Salvador
2017-06-29 6:22 ` Takashi Matsuzawa
2017-06-29 19:41 ` Otavio Salvador
2017-05-26 8:09 ` dynamic-layers? Takashi Matsuzawa
2017-05-26 13:51 ` Patrick Ohly [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=1495806717.16923.120.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=tmatsuzawa@xevo.com \
--cc=yocto@yoctoproject.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.