Producing docker or some other container with yocto is not impossible, but it's a huge maintenance headache. From my experience every developer team wants 'their stuff' in it, and of course they never clean up something they no longer need. So the artefact grows in size indefinitely. There's also the problem of distributing it, and ensuring everyone is on the latest version. It also doesn't really match the actual target hardware: just the userspace root filesystem is the same.
I'd say using Yocto+qemu directly is better overall, if you set up sstate infrastructure so that no one has to do heavy builds with their feeble laptops. Alex On Thu, 25 Jan 2024 at 10:37, Aleksandar Nikolic <an...@live.com> wrote: > > Hi, > > is there a way to use Yocto for development on the host as well? Usually it > is easier to develop code and run some basic testing on the host, however, I > would like to avoid to have to set up the same (or at least a similar) > environment by using Docker for example - some of the issues being having the > same versions of dependencies and their config files, the same or similar > compiler flags, etc. - this would be a lot of work in Docker after an from > e.g. Kirkstone to Scarthgap. > > I know we could use the SDK and run the code in QEMU, but this also requires > a "bit more" work, is however, IMHO, better than using Docker for the same > purpose? > > Any thoughts, ideas or proposals? > > Aleksandar > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62286): https://lists.yoctoproject.org/g/yocto/message/62286 Mute This Topic: https://lists.yoctoproject.org/mt/103951003/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
