I've updated git.yoctoproject.org (meta-xilinx and meta-xilinx-tools) and gotten
the Yocto Project branches synced.
--Mark
On 4/30/23 2:40 PM, Mark Hatle wrote:
On 4/30/23 7:04 AM, Maciej Nowak wrote:
Hello,
README.md meta-petalinux
(https://github.com/Xilinx/meta-petalinux/blob/rel-v2022.2/README.md
<https://github.com/Xilinx/meta-petalinux/blob/rel-v2022.2/README.md>) lists
quite a long list of dependencies coming from various sources. Several layers
come from https://git.yoctoproject.org <https://git.yoctoproject.org> but are
also available on Xilinx's GitHub. For example, meta-xilinx layer is listed as
coming from https://git.yoctoproject.org/meta-xilinx
<https://git.yoctoproject.org/meta-xilinx> where the last commit on honister
branch is from 2022-08-31. However repository
https://github.com/Xilinx/meta-xilinx/tree/honister
<https://github.com/Xilinx/meta-xilinx/tree/honister> (also honister branch) has
last commit from 2022-10-11 and is quite ahead on git.yoctorepository.org
<http://git.yoctorepository.org>. repo's manifest
https://github.com/Xilinx/yocto-manifests/blob/rel-v2022.2/default.xml
<https://github.com/Xilinx/yocto-manifests/blob/rel-v2022.2/default.xml> selects
all possible repositories from github.com/Xilinx <http://github.com/Xilinx>.
git.yoctoproject.org only has Yocto Project branches.
github.com has both PetaLinux and Yocto Project branches. We work on
github.com first, and then push to Yocto Project servers once it "works".
(We're currently behind on Langdale and Mickledore, I have a todo to push it
tomorrow. But this isn't the intended behavior.)
rel-v2022.1 is a PetaLinux branch, and is only compatible with other PetaLinux
layers. You should pull ALL of the layers with that branch from
github.com/Xilinx/....
So, which repositories should I use? Listed in readme, from
git.yoctorepository.org <http://git.yoctorepository.org> or not-listed but
updated?
If you are syncing to PetaLinux all layers should come from github.com/Xilinx.
If you are syncing to community branches, then you should pull from the
community upstreams. See layers.openembedded.org.
In addition I have to mention that list of required layers for meta-petalinux is
large, even by pulling the minimum required set it affects greatly bitbake run
time (especially when modifying one of global config file like machine and
recipes need to be parsed again). While I understand the need for such layer,
pulling support for web browsers, virtualization, ROS and Jupyter is quite large
overhead when working on quite simple embedded system
Yes, PetaLinux requires a LARGE number of things. You are expected to use the
matching layers and versions. Remember PetaLinux is a "place to get started",
it's NOT a go to production system. PetaLinux does NOT get security updates,
on-going bug fixes, etc.
So if you use _honister_ that is a community branch name. That SHOULD be the
same on both github.com and git.yoctoproject.org. All other layers go to their
upstream source.
If you use 'rel-v2022.2', you should use 'repo' and the yocto-manifests
repository to have everything synced down for you from the referenced locations.
You can attempt to assemble it yourself, but this was never tested and is
only
minimally "supported".
--Mark
Regards,
Maciej Nowak
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5237):
https://lists.yoctoproject.org/g/meta-xilinx/message/5237
Mute This Topic: https://lists.yoctoproject.org/mt/98592580/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
