Keith Smiley
Keith Smiley
For reference here's a workaround that I think will work in the meantime https://github.com/envoyproxy/envoy-mobile/pull/2039
lets change the api to just require shas. i don't think we want to encourage folks to sidestep that and we have the helper to generate them anyways
For releases where you don't want debug info you should pass `--compilation_mode=opt` to bazel
Ah right, because it wants to give you debug info in case you need it for crash reports. You can either strip the final binary (maybe `--strip=always` works?) or you...
I think the crash reporting case is why it is, probably better to knowingly have to strip than to forget to enable -g when you need it and not be...
looks like you need to patch in an empty BUILD file at the root of the repo since that repo has them in nested dirs but not at the root?
you should actually try and sidestep this entirely by using the bzlmod googleapis repo. if you don't it can lead to ODR violations since there will be 2 in the...
I believe fixed by https://github.com/bazelbuild/bazel/pull/25709
nice, i think that would work in a pinch, but in our case we have ~40 targets being built from sdists, so it might be a bit too much overhead
I think the most forward looking solution would be too add a custom feature to libraries always and users could define flags based on that feature in their toolchains. but...