4 ms·
Sort of expected being a Google project but Istio [1] is being built using Envoy. Google is involved but Envoy [2] is owned by Lyft and is also using Bazel. 1.
by moderation 9y ago
Sort of expected being a Google project but Istio [1] is being built using Envoy. Google is involved but Envoy [2] is owned by Lyft and is also using Bazel.
1. https://github.com/istio/istio/blob/master/devel/README.md#setting-up-bazel https://github.com/istio/istio/blob/master/devel/README.md#s...
2. https://github.com/lyft/envoy/blob/master/DEVELOPER.md https://github.com/lyft/envoy/blob/master/DEVELOPER.md
- kevinburke 9y agofor the record - this is not a Google project, I'm not a Google employee. I just put the Go license on it because I borrowed some of the code and didn't want to deal with the hassle of relicensing etc. I'm interested in Bazel because of the speed/caching parts, and because Go might be headed in that direction soon.
- justinsaccount 9y agoNeat.. For go I haven't really thought about using it, but I've been working on a project that uses a bunch of bleeding edge C libs. Building the project involves building 3 repos from different git branches before building my little C program. Literally just git clone && checkout && ./autogen.sh && ./configure && make install 3 times. I'd love if I could just make a BUILD file for bazel and be able to just have $MAGIC happen. Especially since it looks like the bazel c target has 'linkstatic' for building a static binary.
- kevinburke 9y agoit's getting there... see the Travis CI config for getting bazel for this repo specifically, or, https://github.com/bazelbuild/rules_go https://github.com/bazelbuild/rules_go has go-specific instructions