Closed paoloturim closed 8 months ago
@paoloturim
Thanks for the feedback.
Yocto collects a lot of opensource and 3rd party packages. All the package are maintained by 3rd-party organizations and companies. Also in Yocto document, it suggests to set up local mirror file server to get rid of this kind of problem.
If you're building a completely new environment, it's not recommended to use hardknott. Because hardknott has been EOL for a long time.
We keep the "download" and "sstate" cache directories on our CI server, so we can build them as well.
BR, Ray
MACHINE=pico-imx8mm DISTRO=fsl-imx-xwayland source tn-setup-release.sh -b build-xwayland
bitbake imx-image-core
Finally I managed to generate my Kirkstone image for pico-imx8mm Using native Ubuntu 22.04 (non-docker) But, not without having to give these two commands below: bitbake rust-llvm-native -c cleansstate bitbake rust-llvm-native
https://developer.technexion.com/docs/building-an-image-in-docker-container
Hi,
I am facing problems using the link above and the commands below (Note: my internet is of excellent quality):
sudo docker run -it -u jenkins -v ${directory_in_host_machine}:${directory_in_docker} tn-develop-ubuntu bash
repo init -u https://github.com/TechNexion/tn-imx-yocto-manifest.git -b hardknott_5.10.y-stable -m imx-5.10.72-2.2.0-2022Q2.xml repo sync -j8 WIFI_FIRMWARE=y DISTRO=fsl-imx-xwayland MACHINE=pico-imx8mm source tn-setup-release.sh -b build-xwayland-pico-imx8mm