4 ms·
I was hoping one can setup a "modern" C development environment without resorting to Docker. Using Docker for setup a C development environment indicates that
by hsn915 3y ago
I was hoping one can setup a "modern" C development environment without resorting to Docker.
Using Docker for setup a C development environment indicates that there are too many moving parts and the development environment is essentially very complex and that there's nothing that one do about it.
I wish more people would write such guides with the aim of reducing the development environment to its essentials that can be installed system-wide without being disruptive and thus not needing "Docker".
- snvzz 3y agoUsing docker merely ensures the environment can be quickly reproduced anywhere, anytime it is needed. It is entirely optional, yet extremely useful.
- piaste 3y agoOh, you can surely install a minimal development environment system-wide. Once. Containers just enable you to do it more than once. And they leave you a plaintext napkin with the list of stuff you installed.
- kkoste 3y agoI have a C project template for VSCode that I just copy whenever I start a new C-project. Inspiration for it was mostly because I don't want to rewrite the same CMake code constantly. But I think there are a lot of these kind of projects floating around out there on github. I use mingsys though . But theoretically it should be no trouble to change the compiler.
- P_I_Staker 3y agoThat wouldn't be very "modern"
- legobmw99 3y agoObviously it is goal dependent, but if you eventually want your code to run on a variety of machines and systems, I find docker to actually be a barrier. Having a different environment in CI than local can be annoying, but it’s also the first time you are forced to confront the “but it runs on my laptop!” problem