From: Mark Hatle <mark.hatle@windriver.com>
To: Mike Looijmans <mike.looijmans@topic.nl>,
<openembedded-core@lists.openembedded.org>
Subject: Re: Recipe versions and layer confusion
Date: Thu, 5 Oct 2017 09:59:01 -0500 [thread overview]
Message-ID: <67768df5-8082-3433-715c-1c2bfde6f973@windriver.com> (raw)
In-Reply-To: <8b6c437e-c5b6-d242-5e1c-b19406153c76@topic.nl>
On 10/5/17 9:49 AM, 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.
Typically the version is selected by whichever PV is 'higher'. However there
are many ways to change this behavior.
The primary way is for a configuration file (often the machine configuration) to
defined a preferred version. I.e.
PREFERRED_VERSION_arm-trusted-firmware = "2017.1"
Most likely there is a line like that someone in meta-xilinx.
Additional ways would be to have a recipe define itself as never the default
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
> ..
The layer priority does not directly affect recipe selection. It may if you
have two layers of the -same- version.
--Mark
> so that means that my meta-topic should win even if my PV were lower, right?
>
>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Products
> Materiaalweg 4, NL-5681 RJ Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> E-mail: mike.looijmans@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
> Visit us at the Space Tech Expo Europe (Stand E-71)
>
next prev parent reply other threads:[~2017-10-05 14:59 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 [this message]
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
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=67768df5-8082-3433-715c-1c2bfde6f973@windriver.com \
--to=mark.hatle@windriver.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