3 ms·
I'm ignorant about C development and its practices, but installing development dependencies using the distro's package manager has always seemed very wrong to m
by diego_sandoval 3y ago
I'm ignorant about C development and its practices, but installing development dependencies using the distro's package manager has always seemed very wrong to me.
Doing it inside a container solves the portability problem, but you're still using a Linux distribution's package manager to get the dependencies of your project, which makes no sense to me at a fundamental level, even if it "works" in practice.
Is vendoring the only somewhat sane way of doing dependency management in C?
- seabrookmx 3y agoAbout 10 years ago when I wrote C++ for a living, vendoring was the solution. When you look at flatpak, snap etc. that's effectively what they do.. vendor all their libs. I would hope that tools like conan and vcpkg solve this now on the developer side? I don't have much experience with them though. You still have to deal with libc though, which means you likely need to containerize to avoid issues with old versions or distros that use something other than glibc (musl or bionic, for example). It's a lot more complex with C/C++ to build fully static binaries than it is in something like rust or GoLang.