News for hackers. Stuff that matters.
Re:A Modern C Development Environment by cushychicken on Thursday August 10, 2023 @10:16PM (#37084320)
Docker is a godsend when you're a solo embedded consultant and a former customer comes to you five years later with an urgent firmware feature request and cash in hand.

If you don't have the exact machine any more, then it's "Good luck getting the toolchain and build environment from the vendor!"

Docker has saved my bacon at least twice in this manner.

Re:A Modern C Development Environment by publicmail on Thursday August 10, 2023 @10:37PM (#37084444)
Yep. I use VMs though. I still have to build for some embedded platforms that are based on the 2.4 Linux kernel…
Re:A Modern C Development Environment by fbdab103 on Friday August 11, 2023 @01:01AM (#37085270)
Would a five year old Docker image still work? I mean, probably, but for long term maintenance of a build environment, I would feel significantly better with a VM.
Re:A Modern C Development Environment by vidarh on Friday August 11, 2023 @05:26AM (#37086723)
I have Docker images older than that I use regularly.

For things where kernel changes matter, sure a VM may provide better isolation, but should you ever run into problems running your older Docker images, you can easily solve that by spinning up a VM to run Docker in as a worst case fallback.

Docker strikes a nice balance of ease of integration and sufficient isolation for most situations.

Re:A Modern C Development Environment by raverbashing on Friday August 11, 2023 @01:58AM (#37085549)
Yeah (and I agree) but it doesn't have to be docker

It can be a vm, even a chroot.

Also the compatibility questions and docker "opacity" come to mind.

A QEMU VM sounds like a better propositions

Re:A Modern C Development Environment by cushychicken on Friday August 11, 2023 @11:25AM (#37089753)
I'd consider a VM, and I've used them before, but I've found Docker gives the advantage of forcing me to be thorough in my toolchain docs, and portable to CI pipelines.

chroot sounds like nothing but a headache.

QEMU VM, I don't even understand the potential advantage of lol

Re:A Modern C Development Environment by hot_gril on Friday August 11, 2023 @03:49PM (#37093143)
QEMU for emulating different hardware I guess. Actually I was wondering how you test firmware repeatably without hardware emu; never dealt in firmware myself.
Re:A Modern C Development Environment by cushychicken on Friday August 11, 2023 @05:07PM (#37094045)
The only way you really can is with hardware in the loop, in my opinion.

People try with mocks and stubs, but hardware in the loop is the only way you can know your firmware works as expected on device.