From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Recipe versions and layer confusion
Date: Fri, 06 Oct 2017 10:18:38 +1300 [thread overview]
Message-ID: <4488567.fOZDuWkyH7@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <8b6c437e-c5b6-d242-5e1c-b19406153c76@topic.nl>
Hi Mike,
On Friday, 6 October 2017 3:49:28 AM NZDT Mike Looijmans wrote:
> I'm confused.
>
> Layer "meta-xilinx" defines:
>
> recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2017.1.bb
>
> This recipe is too old for my liking, so I made a newer one in "meta-topic"
>
> recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2017.3.bb
>
>
> Much to my surprise, when I build, OE picks the 2017.1 version and not the
> 2017.3 version.
>
> bitbake-layers show-layers reveils:
> ..
> meta-xilinx /home/mike/projects/zynq-platform/meta-xilinx 5
> meta-topic /home/mike/projects/zynq-platform/meta-topic 6
> ..
>
> so that means that my meta-topic should win even if my PV were lower, right?
At face value I would have to agree - it doesn't sound like it's working the
way it should.
What does bitbake-layers show-recipes arm-trusted-firmware show ?
Another diagnostic would be to do bitbake -DDD arm-trusted-firmware and see if
it gives any explanation as to why it's picking the older version (you'll have
to wade through all of the other irrelevant debug info though).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2017-10-05 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 14:49 Recipe versions and layer confusion Mike Looijmans
2017-10-05 14:59 ` Mark Hatle
2017-10-05 15:11 ` Mike Looijmans
2017-10-05 15:19 ` Leonardo Sandoval
2017-10-05 21:44 ` Leonardo Sandoval
2017-10-05 22:10 ` Andre McCurdy
2017-10-07 9:15 ` Mike Looijmans
2017-10-05 21:18 ` Paul Eggleton [this message]
2017-10-07 2:33 ` 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=4488567.fOZDuWkyH7@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@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