Multiple machines has a heavy cost, as you effectively double the amount of builds (and build times) just so you can enable or not some features in the kernel on the exact same hardware. I would suggest to keep the same machine and same distro, and just make multiple images (maybe even in the same bitbake invocation) that include (or not) needed kernel modules and userspace packages.
Alex On Thu, 25 Jan 2024 at 10:38, Aleksandar Nikolic <an...@live.com> wrote: > > Hi, > > I know similar questions have been posted before, but still I have a few > things to clarify. > > We are using the same hardware for multiple projects, which means some > projects support some interfaces (e.g. bluetooth - Y, WiFi - N), while others > some other interfaces (e.g. bluetooth - N, WiFi - Y). Of course I don't want > support for bluetooth in case we don't need it. > > AFAIK there are (at least) two ways to address this: [1] with multiple > MACHINE configs and [2] with multiple IMAGE recipes. > > For MACHINE_FEATURES the Yocto documentation states the following: Specifies > the list of hardware features the MACHINE is capable of supporting. I am > reading as: [1] there is only one MACHINE conf per target and [2] > MACHINE_FEATURES does not change. This leaves us with the second option: we > should have multiple image recipes and each recipe should define for itself > what package groups it will include (e.g. bluetooth support, wifi support, > etc.). However, this doesn't play nicely with e.g. kernel fragments. If the > product does not need to support bluetooth, I also don't want the software > stack compiled in my kernel, however, I don't have a variable to use in my > kernel recipe. Any thoughts to this? > > Aleksandar > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62287): https://lists.yoctoproject.org/g/yocto/message/62287 Mute This Topic: https://lists.yoctoproject.org/mt/103951016/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
