Looks like Linux Distro Sources and Toolchain links are broken.
Linux Distro Source points only to archive with Yocto downloads directory contents, but not to Yocto recipes tree. Toolchain links are points only to some custom scripts, but not for ARM-gcc compiler and related.
Can you provide correct links to download files to be able to build customized Linux image. In my project I’m using Qt5Core library. It is absent in default image.
There is still the problem with traversing symlinks with repo tool. Old repo version is not working anymore. It requires python2 while swi-linux-src/.repo/repo/main.py requires python3. New version stops with “swi-linux-src/kernel/arch/arm/mach-msm: traversing symlinks not allow”.
Looks like meta-swi-extras/create_bin_layer.sh script is broken. So, it’s a question how to use “PROD=custom_product_name make” to use specific machine configuration for yocto build.
The build system starting to look pre-build proprietary binaries in meta-swi-mdm9x28-custom_product_name-bin directory, which needs to be created.
Yes, it works well. I’m making my own images, with custom device tree, custom packages and so on. For now I patched existing machine and distribution configuration files, to be able to test everything related to Linux image.
However, now I would like to make my own product and distribution configuration, to not touch existing files in your repository.
This is that I exactly done. I only used older repo tool (1.13 version), because of incompatibility in symlinks processing in later repo versions.
Build scripts is just starting to search pre-built binaries in the non-existing directory. So, I found this script to create a new binary layer for new product description, however, looks like it does not work anymore.
If I’m making symlink meta-swi-mdm9x28-custom_product_name-bin to meta-swi-mdm9x28-wp-bin, then build is completed successfully. But is this correct way? I suppose not.
Build script is strictly assuming that proprietary binaries for each product will be in meta-swi-extras directory.
So, as I understand, it’s not recommended to make new set of distro, machine, image configurations (as it usually for Yocto-based distributions). Instead of this make changes in local.conf, patch and make .bbappend for existing packages, like kernel.
Right?
P.S. And I cannot find a way to specify to bootloader what device tree to use, like I did with u-boot on other platforms. Is this possible for WP76xx/77xx?
