Hello community, I have a project where I work with two different image recipes. One is meant for production and targets NAND, another one for SD CARD. The second one is basically a tiny image that contains scripts to flash the NAND with the production image.
My question is: what's the recommended way to manage these two images in terms of MACHINE and UBOOT_CONFIG? How I did till now: just changed the weak default for UBOOT_CONFIG found in the machine.conf depending on the image I was baking. This does not look good to me because it clutters the deploy dir for the given machine with unrelated build artifacts. A better alternative comes to my mind: the physical board is just one, so it makes sense that both images should refer to the same MACHINE variable. The machine.conf provides a weak assignment for UBOOT_CONFIG and image recipes should change its value depending on their needs. But I suspect that since the data store for each recipe (comprised image recipes) is a local coly, such assignment does not work. Then only two bins are left: mess up the deploy dir as I did till now OR use two different machines with different weak defaults, which I think is somewhat wrong as the hardware is one. Can you help me sort this out? Thanks
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63540): https://lists.yoctoproject.org/g/yocto/message/63540 Mute This Topic: https://lists.yoctoproject.org/mt/107461549/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
