* Update visibility tags
Add some tags to the bazel build that we can leverage internally to help
control visibility in the Google build system.
* review feedback
* Add needed visibility tag
* Update visibility tags
Add some tags to the bazel build that we can leverage internally to help
control visibility in the Google build system.
* review feedback
Add use_default_shell_env = True to protoc invocation to mirror
what the protobuf cc_proto_library & co are doing
Fixes a failure in invocing protoc when it is build in a non-default
environment (e.g. with a custom LD_LIBRARY_PATH)
A corresponding update to the build system will need to occur before this is submitted.
Add a way of labelling in build configuration meta-visibility-rules, so that these can be leveraged to restrict visibility in Google's build system upstream.
* Reduce the usage of _xds Bazel rules
* Inject DISABLED_XDS_PROTO_IN_CC to admin_services_end2end_test
* Remove _xds suffix Bazel rules completely
* Remove the _xds rules from imports
* Simplify the ifndef usage in admin_services_end2end_test
This fix the following error when compiling:
error: #error C++11 or greater detected by the library. BENCHMARK_HAS_CXX11 is defined.
12 | #error C++11 or greater detected by the library. BENCHMARK_HAS_CXX11 is defined.
| ^~~~~
Signed-off-by: Clément Péron <peron.clem@gmail.com>
* [xDS Proto] Update Bazel dependencies
* Include transitive deps required by xDS proto libraries
* The Golang deps come from protoc-gen-validate project
* Adding a new submodule: opencensus-proto
* Add the new submodule to .bazelignore
* Update WORKSPACE file to initialize googleapis
* Remove WORKSPACE override
* Adopt reviewer's advice
A breaking C-level API change was made in Python 3.9 which old versions
of Cython cannot handle. Since Bazel prescribes a single version of
dependency instead of ranges, like in setuptools, we must update this to
keep our downstream users working properly.
As a side note, since it was a point of confusion while debugging this,
interpreter versions installed by pyenv must be set *globally* rather
than just locally for Bazel to pick them up, since local pyenv
configuration will not be picked up from within the sandbox.