Hi Vinayak I believe that the best way to prepare debug and prod images is to create include file (.inc) with base set of packages and features and then add two .bb recipes, one for prod and one for debug - every of this recipes will need to include the `.inc` file. You could name them `base-image-prod.bb` and `base-image-debug.bb`. This way you could run either prod or debug builds by running `bitbake base-image-debug` or `bitbake base-image-prod`.
As for the machine, this would need to be set in local.conf every time you want to switch the machine. To simplify this process, for the management of the configuration of the entire build (including the selection of debug / prod image or machine configuration), I recommend the kas[1] project with the very helpful kas-container tool. [1] https://github.com/siemens/kas Regards, Tomasz Żyjewski Embedded Systems Engineer GPG: 5C495EA3EBEECA59 https://3mdeb.com | @3mdeb_com
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56332): https://lists.yoctoproject.org/g/yocto/message/56332 Mute This Topic: https://lists.yoctoproject.org/mt/89469781/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
