4 ms·
Not at all. They make cross compiling fairly trivial, and give teams a way of managing cross compiled dependencies. This was vital a few years ago for things li
by coderenegade 3y ago
Not at all. They make cross compiling fairly trivial, and give teams a way of managing cross compiled dependencies. This was vital a few years ago for things like torch and even opencv, where deploying on anything other than x86 meant you were probably on your own, and you almost certainly wanted control over the compiler flags.
That's just one example, though. It also lets you standardize the dev environment (work directly out of the build container directly, or use your host OS and run unit tests in a local build), and it allows for easy, standardized testing within the same environment.
- lmm 3y ago> Not at all. They make cross compiling fairly trivial, and give teams a way of managing cross compiled dependencies. How so? A container is the same architecture as the host, how does that help with cross compiling?
- coderenegade 3y agoYou combine qemu with docker. You can then run arm containers and compile your code locally for deployment to an arm board.
- lmm 3y agoQemu is the part that's making that possible though. What's docker adding?
- imtringued 3y agoThe ability to kickstart the whole process with a few commands, possibly just a single bash script.
- lmm 3y agoSo what Vagrant already did?