From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: nicolas.wirth@speedgoat.ch
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] How to switch between package version ?
Date: Wed, 16 Aug 2023 15:05:40 +0300 [thread overview]
Message-ID: <ZNy7lBOvfDQheQ5j@nuoska> (raw)
In-Reply-To: <19617.1692186953072162853@lists.yoctoproject.org>
Hi,
On Wed, Aug 16, 2023 at 04:55:53AM -0700, Nicolas Wirth via lists.yoctoproject.org wrote:
> Hi Mikko, thank you for you're answer which was very insightful.
>
> >
> > If that is not available, check if you can change the branch of an existing
> > meta layer to provide what you need. Note that mixing
> > layer branch names is frequently possible with minor changes, e.g. using
> > meta-security master branch with kirkstone LTS poky.
>
> Could I ask you to elaborate on this subject or share some resources about mixing layer branches ?
There isn't much documentation. It's more about just doing it and resolving any issues
you find. For example BSP deliveries from vendors frequently only support older yocto branches.
These should not dictate the poky release for the full SW stack when for example only kernel
and bootloader are needed from their delivery. Thus using older BSP layer with the kernel
and other recipes with a newer poky is a matter of configuring the build system and resolving
any build failures from e.g. newer poky and gcc. The layer compatibility setting meant to warn
and prohibit from doing this, but this can be overruled in other layers by setting
e.g. LAYERSERIES_COMPAT_security-layer += "mickledore kirkstone" in layer.conf of your own
layers. If large parts of a layer (BSP) are not needed in your configuration and cause
build issues, then those can be hidden by setting BBMASK for those paths.
Hope this helps,
-Mikko
next prev parent reply other threads:[~2023-08-16 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 10:54 How to switch between package version ? Nicolas Wirth
2023-08-16 11:13 ` [yocto] " Mikko Rapeli
2023-08-16 11:55 ` Nicolas Wirth
2023-08-16 12:05 ` Mikko Rapeli [this message]
2023-08-16 14:45 ` Nicolas Wirth
2023-08-16 15:02 ` [yocto] " Alex Kiernan
2023-08-16 15:30 ` Alexander Kanavin
2023-08-16 15:32 ` Alexander Kanavin
2023-08-17 4:41 ` Mikko Rapeli
2023-08-17 7:37 ` Alexander Kanavin
[not found] ` <177BD8C48AE805D0.8497@lists.yoctoproject.org>
2023-08-17 7:47 ` Mikko Rapeli
2023-08-17 10:51 ` Nicolas Wirth
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=ZNy7lBOvfDQheQ5j@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=nicolas.wirth@speedgoat.ch \
--cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox