2 ms·
> It forces hermetic build and test environments; how would that ever work if you want to build software to be packaged in a linux distro where your software h
by jcelerier 6y ago
> It forces hermetic build and test environments;
how would that ever work if you want to build software to be packaged in a linux distro where your software has to comply with $VERSION of every library provided by the distro ?
- steeve 6y agoIt is focused on producing static (or mostly static) binaries. Obviously not everything can be in the sandbox, but in the Bazel world, it takes over the build of all your dependencies (as it is also a package overlay).
- gravypod 6y agoBazel isn't really designed for dynamic linking applications. You can include system libraries if you need: https://groups.google.com/g/bazel-discuss/c/Ndd820uaq2U https://groups.google.com/g/bazel-discuss/c/Ndd820uaq2U You'd also need to make sure everything is marked as `linkstatic=false`, but I'm not sure if that would work correctly. But, in the end of the day, you're going against the grain of bazel here. Bazel expects to statically link everything to make distribution to heterogeneous environments simpler.
- jcelerier 6y agoright, but then understand that if someone wants to create a software for which a goal is to be packaged & distributed by e.g. Debian, homebrew, msys2, Fedora, CentOS..., this is an absolute non-starter.