From: Mike Looijmans <mike.looijmans@topic.nl>
To: Andre McCurdy <armccurdy@gmail.com>,
Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: Recipe versions and layer confusion
Date: Sat, 7 Oct 2017 11:15:22 +0200 [thread overview]
Message-ID: <f5a0f8aa-b2f4-7d3d-eb17-1206ee7d41f2@topic.nl> (raw)
In-Reply-To: <CAJ86T=WdwVG5sqj70FZ-AEw7+CYu0dNvqqXBCxwp2jPP_bogcQ@mail.gmail.com>
On 06-10-17 00:10, Andre McCurdy wrote:
> On Thu, Oct 5, 2017 at 2:44 PM, Leonardo Sandoval
> <leonardo.sandoval.gonzalez@linux.intel.com> wrote:
>> On Thu, 5 Oct 2017 10:19:18 -0500
>> Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> wrote:
>>
>>> On Thu, 5 Oct 2017 16:49:28 +0200
>>> Mike Looijmans <mike.looijmans@topic.nl> 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?
>
> Yes. The comments in bitbake/lib/bb/providers.py -> findBestProvider()
> explain the process pretty well:
>
> If there is a PREFERRED_VERSION, find the highest-priority bbfile
> providing that version. If not, find the latest version provided by
> an bbfile in the highest-priority set.
>
> The only caveat is that if PREFERRED_VERSION contains a wildcard (%)
> and matches more than one available version then all bets are off and
> results may be unpredictable. It's up to the user to ensure that
> doesn't happen.
>
> Note that looking at the meta-xilinx recipe it seems that PV is set
> manually and doesn't follow the recipe name, so depending on how you
> set PV in your new recipe, it may not be completely obvious which
> recipe is actually being used?
>
> https://github.com/Xilinx/meta-xilinx/blob/master/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2017.1.bb
>
Yeah, that turned out to be the problem. The recipe is versioned as
"2017.1" but that is not the version it will actually build.
"bitbake-layers show-recipes arm-trusted-firmware" reveiled the true
versions, as Paul suggested, and that explained the strange choices.
--
Mike Looijmans
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-07 9:15 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 [this message]
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=f5a0f8aa-b2f4-7d3d-eb17-1206ee7d41f2@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=armccurdy@gmail.com \
--cc=leonardo.sandoval.gonzalez@linux.intel.com \
--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