grpc/third_party/BUILD

exports_files([
    "gtest.BUILD",
    "zlib.BUILD",
    "twisted.BUILD",
    "yaml.BUILD",
    "incremental.BUILD",
    "zope_interface.BUILD",
    "constantly.BUILD",
    "cython.BUILD",
    "six.BUILD",
    "enum34.BUILD",
    "futures.BUILD",
    "protobuf.patch",
    "protoc-gen-validate.patch",
])
Packs contents of WORKSPACE into a bzl function, so that it can be resued by other projects, and simplifies cares build. 7 years ago			`exports_files([`
			`"gtest.BUILD",`
			`"zlib.BUILD",`
Add python bazel deps needed to run resolver component tests 7 years ago			`"twisted.BUILD",`
			`"yaml.BUILD",`
			`"incremental.BUILD",`
			`"zope_interface.BUILD",`
			`"constantly.BUILD",`
Workspace changes to build gRPC Python with Bazel - Include new rules from bazelbuild/rules_python, which allow for importing pip dependencies with Bazel. - Make Cython BUILD file visible to WORKSPACE. - Use a custom requirements file for Bazel python. This is added to allow for requirements previously added only during build steps. 6 years ago			`"cython.BUILD",`
Separate py_grpc_library and py_proto_library. By popular demand, we'll now be offering separate py_grpc_library and py_proto_library targets sharing the same interface as within google3. This change necessitated some modifications to how we pull in our own Python-level dependencies and how we make those available to those pulling in our project via Bazel. There is now a grpc_python_deps() Bazel workspace rule that pulls in the appropriate dependencies, which should be called from the client project's WORKSPACE file. A test has been added to the bazel/test/ directory to verify that this behavior works as intended. It's worth noting that the protobuf repository's usage of Starlark bind() caused a great deal of trouble in ensuring that we could also pull in six. This change also required a change in the way generated proto code is imported in the channelz and health-check modules, as well as in their associated tests. We were importing them two different ways, each relative. This resulted in two different module objects being imported into the process, which were incompatible. I am not sure exactly what caused this behavior to begin, as this should have been possible before this PR. As a workaround, I am simply trying two different absolute imports and using the one that works. This should function both inside and outside of Bazel environments. 5 years ago			`"six.BUILD",`
			`"enum34.BUILD",`
			`"futures.BUILD",`
Make patch work for downstream dependencies 4 years ago			`"protobuf.patch",`
[xDS Proto] Update Bazel build dependencies for Envoy API (#29219) * [xDS Proto] Update Bazel build dependencies for Envoy API * Remove protoc_gen_validate as a submodule * Remove unused import 3 years ago			`"protoc-gen-validate.patch",`
Packs contents of WORKSPACE into a bzl function, so that it can be resued by other projects, and simplifies cares build. 7 years ago			`])`