|
|
|
|
workspace(name = "com_github_grpc_grpc")
|
|
|
|
|
|
|
|
|
|
load("//bazel:grpc_deps.bzl", "grpc_deps", "grpc_test_only_deps")
|
|
|
|
|
|
|
|
|
|
grpc_deps()
|
|
|
|
|
|
|
|
|
|
grpc_test_only_deps()
|
|
|
|
|
|
|
|
|
|
load("//bazel:grpc_extra_deps.bzl", "grpc_extra_deps")
|
|
|
|
|
|
|
|
|
|
grpc_extra_deps()
|
|
|
|
|
|
|
|
|
|
load("@bazel_toolchains//rules/exec_properties:exec_properties.bzl", "create_rbe_exec_properties_dict", "custom_exec_properties")
|
|
|
|
|
|
|
|
|
|
custom_exec_properties(
|
|
|
|
|
name = "grpc_custom_exec_properties",
|
|
|
|
|
constants = {
|
|
|
|
|
"LARGE_MACHINE": create_rbe_exec_properties_dict(
|
|
|
|
|
labels = {
|
|
|
|
|
"os": "ubuntu",
|
|
|
|
|
"machine_size": "large",
|
|
|
|
|
},
|
|
|
|
|
),
|
|
|
|
|
},
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
|
|
|
|
|
|
|
|
|
|
http_archive(
|
|
|
|
|
name = "build_bazel_rules_android",
|
|
|
|
|
sha256 = "cd06d15dd8bb59926e4d65f9003bfc20f9da4b2519985c27e190cddc8b7a7806",
|
|
|
|
|
strip_prefix = "rules_android-0.1.1",
|
|
|
|
|
urls = ["https://github.com/bazelbuild/rules_android/archive/v0.1.1.zip"],
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
load("//third_party/android:android_configure.bzl", "android_configure")
|
|
|
|
|
|
|
|
|
|
android_configure(name = "local_config_android")
|
|
|
|
|
|
|
|
|
|
load("@local_config_android//:android_configure.bzl", "android_workspace")
|
|
|
|
|
|
|
|
|
|
android_workspace()
|
|
|
|
|
|
|
|
|
|
# Prevents bazel's '...' expansion from including the following folder.
|
|
|
|
|
# This is required because the BUILD file in the following folder
|
|
|
|
|
# will trigger bazel failure when Android SDK is not configured.
|
|
|
|
|
# The targets in the following folder need to be included in APK and will
|
|
|
|
|
# be invoked by binder transport implementation through JNI.
|
|
|
|
|
local_repository(
|
|
|
|
|
name = "binder_transport_android_helper",
|
|
|
|
|
path = "src/core/ext/transport/binder/java",
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
# Prevents bazel's '...' expansion from including the following folder.
|
|
|
|
|
# This is required to avoid triggering "Unable to find package for @rules_fuzzing//fuzzing:cc_defs.bzl"
|
|
|
|
|
# error.
|
|
|
|
|
local_repository(
|
|
|
|
|
name = "ignore_third_party_utf8_range_subtree",
|
|
|
|
|
path = "third_party/utf8_range",
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
load("@rules_python//python:pip.bzl", "pip_parse")
|
|
|
|
|
|
|
|
|
|
pip_parse(
|
|
|
|
|
name = "grpc_python_dependencies",
|
|
|
|
|
requirements_lock = "@com_github_grpc_grpc//:requirements.bazel.txt",
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
load("@grpc_python_dependencies//:requirements.bzl", "install_deps")
|
|
|
|
|
|
|
|
|
|
install_deps()
|
|
|
|
|
|
|
|
|
|
load("@com_google_protobuf//bazel:system_python.bzl", "system_python")
|
[protobuf] Upgrade third_party/protobuf to 22.x (#32606)
The very non-trivial upgrade of third_party/protobuf to 22.x
This PR strives to be as small as possible and many changes that were
compatible with protobuf 21.x and didn't have to be merged atomically
with the upgrade were already merged.
Due to the complexity of the upgrade, this PR wasn't created
automatically by a tool, but manually. Subsequent upgraded of
third_party/protobuf with our OSS release script should work again once
this change is merged.
This is best reviewed commit-by-commit, I tried to group changes in
logical areas.
Notable changes:
- the upgrade of third_party/protobuf submodule, the bazel protobuf
dependency itself
- upgrade of UPB dependency to 22.x (in the past, we used to always
upgrade upb to "main", but upb now has release branch as well). UPB
needs to be upgraded atomically with protobuf since there's a de-facto
circular dependency (new protobuf depends on new upb, which depends on
new protobuf for codegen).
- some protobuf and upb bazel rules are now aliases, so `
extract_metadata_from_bazel_xml.py` and `gen_upb_api_from_bazel_xml.py`
had to be modified to be able to follow aliases and reach the actual
aliased targets.
- some protobuf public headers were renamed, so especially
`src/compiler` needed to be updated to use the new headers.
- protobuf and upb now both depend on utf8_range project, so since we
bundle upb with grpc in some languages, we now have to bundle utf8_range
as well (hence changes in build for python, PHP, objC, cmake etc).
- protoc now depends on absl and utf8_range (previously protobuf had
absl dependency, but not for the codegen part), so python's
make_grpcio_tools.py required partial rewrite to be able to handle those
dependencies in the grpcio_tools build.
- many updates and fixes required for C++ distribtests (currently they
all pass, but we'll probably need to follow up, make protobuf's and
grpc's handling of dependencies more aligned and revisit the
distribtests)
- bunch of other changes mostly due to overhaul of protobuf's and upb's
internal build layout.
TODOs:
- [DONE] make sure IWYU and clang_tidy_code pass
- create a list of followups (e.g. work to reenable the few tests I had
to disable and to remove workaround I had to use)
- [DONE in cl/523706129] figure out problem(s) with internal import
---------
Co-authored-by: Craig Tiller <ctiller@google.com>
2 years ago
|
|
|
|
|
|
|
|
system_python(
|
|
|
|
|
name = "system_python",
|
|
|
|
|
minimum_python_version = "3.7",
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
load("@system_python//:pip.bzl", system_pip_parse = "pip_parse")
|
[protobuf] Upgrade third_party/protobuf to 22.x (#32606)
The very non-trivial upgrade of third_party/protobuf to 22.x
This PR strives to be as small as possible and many changes that were
compatible with protobuf 21.x and didn't have to be merged atomically
with the upgrade were already merged.
Due to the complexity of the upgrade, this PR wasn't created
automatically by a tool, but manually. Subsequent upgraded of
third_party/protobuf with our OSS release script should work again once
this change is merged.
This is best reviewed commit-by-commit, I tried to group changes in
logical areas.
Notable changes:
- the upgrade of third_party/protobuf submodule, the bazel protobuf
dependency itself
- upgrade of UPB dependency to 22.x (in the past, we used to always
upgrade upb to "main", but upb now has release branch as well). UPB
needs to be upgraded atomically with protobuf since there's a de-facto
circular dependency (new protobuf depends on new upb, which depends on
new protobuf for codegen).
- some protobuf and upb bazel rules are now aliases, so `
extract_metadata_from_bazel_xml.py` and `gen_upb_api_from_bazel_xml.py`
had to be modified to be able to follow aliases and reach the actual
aliased targets.
- some protobuf public headers were renamed, so especially
`src/compiler` needed to be updated to use the new headers.
- protobuf and upb now both depend on utf8_range project, so since we
bundle upb with grpc in some languages, we now have to bundle utf8_range
as well (hence changes in build for python, PHP, objC, cmake etc).
- protoc now depends on absl and utf8_range (previously protobuf had
absl dependency, but not for the codegen part), so python's
make_grpcio_tools.py required partial rewrite to be able to handle those
dependencies in the grpcio_tools build.
- many updates and fixes required for C++ distribtests (currently they
all pass, but we'll probably need to follow up, make protobuf's and
grpc's handling of dependencies more aligned and revisit the
distribtests)
- bunch of other changes mostly due to overhaul of protobuf's and upb's
internal build layout.
TODOs:
- [DONE] make sure IWYU and clang_tidy_code pass
- create a list of followups (e.g. work to reenable the few tests I had
to disable and to remove workaround I had to use)
- [DONE in cl/523706129] figure out problem(s) with internal import
---------
Co-authored-by: Craig Tiller <ctiller@google.com>
2 years ago
|
|
|
|
|
|
|
|
system_pip_parse(
|
[protobuf] Upgrade third_party/protobuf to 22.x (#32606)
The very non-trivial upgrade of third_party/protobuf to 22.x
This PR strives to be as small as possible and many changes that were
compatible with protobuf 21.x and didn't have to be merged atomically
with the upgrade were already merged.
Due to the complexity of the upgrade, this PR wasn't created
automatically by a tool, but manually. Subsequent upgraded of
third_party/protobuf with our OSS release script should work again once
this change is merged.
This is best reviewed commit-by-commit, I tried to group changes in
logical areas.
Notable changes:
- the upgrade of third_party/protobuf submodule, the bazel protobuf
dependency itself
- upgrade of UPB dependency to 22.x (in the past, we used to always
upgrade upb to "main", but upb now has release branch as well). UPB
needs to be upgraded atomically with protobuf since there's a de-facto
circular dependency (new protobuf depends on new upb, which depends on
new protobuf for codegen).
- some protobuf and upb bazel rules are now aliases, so `
extract_metadata_from_bazel_xml.py` and `gen_upb_api_from_bazel_xml.py`
had to be modified to be able to follow aliases and reach the actual
aliased targets.
- some protobuf public headers were renamed, so especially
`src/compiler` needed to be updated to use the new headers.
- protobuf and upb now both depend on utf8_range project, so since we
bundle upb with grpc in some languages, we now have to bundle utf8_range
as well (hence changes in build for python, PHP, objC, cmake etc).
- protoc now depends on absl and utf8_range (previously protobuf had
absl dependency, but not for the codegen part), so python's
make_grpcio_tools.py required partial rewrite to be able to handle those
dependencies in the grpcio_tools build.
- many updates and fixes required for C++ distribtests (currently they
all pass, but we'll probably need to follow up, make protobuf's and
grpc's handling of dependencies more aligned and revisit the
distribtests)
- bunch of other changes mostly due to overhaul of protobuf's and upb's
internal build layout.
TODOs:
- [DONE] make sure IWYU and clang_tidy_code pass
- create a list of followups (e.g. work to reenable the few tests I had
to disable and to remove workaround I had to use)
- [DONE in cl/523706129] figure out problem(s) with internal import
---------
Co-authored-by: Craig Tiller <ctiller@google.com>
2 years ago
|
|
|
name = "pip_deps",
|
|
|
|
|
requirements = "@com_google_protobuf//python:requirements.txt",
|
[protobuf] Upgrade third_party/protobuf to 22.x (#32606)
The very non-trivial upgrade of third_party/protobuf to 22.x
This PR strives to be as small as possible and many changes that were
compatible with protobuf 21.x and didn't have to be merged atomically
with the upgrade were already merged.
Due to the complexity of the upgrade, this PR wasn't created
automatically by a tool, but manually. Subsequent upgraded of
third_party/protobuf with our OSS release script should work again once
this change is merged.
This is best reviewed commit-by-commit, I tried to group changes in
logical areas.
Notable changes:
- the upgrade of third_party/protobuf submodule, the bazel protobuf
dependency itself
- upgrade of UPB dependency to 22.x (in the past, we used to always
upgrade upb to "main", but upb now has release branch as well). UPB
needs to be upgraded atomically with protobuf since there's a de-facto
circular dependency (new protobuf depends on new upb, which depends on
new protobuf for codegen).
- some protobuf and upb bazel rules are now aliases, so `
extract_metadata_from_bazel_xml.py` and `gen_upb_api_from_bazel_xml.py`
had to be modified to be able to follow aliases and reach the actual
aliased targets.
- some protobuf public headers were renamed, so especially
`src/compiler` needed to be updated to use the new headers.
- protobuf and upb now both depend on utf8_range project, so since we
bundle upb with grpc in some languages, we now have to bundle utf8_range
as well (hence changes in build for python, PHP, objC, cmake etc).
- protoc now depends on absl and utf8_range (previously protobuf had
absl dependency, but not for the codegen part), so python's
make_grpcio_tools.py required partial rewrite to be able to handle those
dependencies in the grpcio_tools build.
- many updates and fixes required for C++ distribtests (currently they
all pass, but we'll probably need to follow up, make protobuf's and
grpc's handling of dependencies more aligned and revisit the
distribtests)
- bunch of other changes mostly due to overhaul of protobuf's and upb's
internal build layout.
TODOs:
- [DONE] make sure IWYU and clang_tidy_code pass
- create a list of followups (e.g. work to reenable the few tests I had
to disable and to remove workaround I had to use)
- [DONE in cl/523706129] figure out problem(s) with internal import
---------
Co-authored-by: Craig Tiller <ctiller@google.com>
2 years ago
|
|
|
requirements_overrides = {
|
|
|
|
|
"3.11": "@com_google_protobuf//python:requirements_311.txt",
|
[protobuf] Upgrade third_party/protobuf to 22.x (#32606)
The very non-trivial upgrade of third_party/protobuf to 22.x
This PR strives to be as small as possible and many changes that were
compatible with protobuf 21.x and didn't have to be merged atomically
with the upgrade were already merged.
Due to the complexity of the upgrade, this PR wasn't created
automatically by a tool, but manually. Subsequent upgraded of
third_party/protobuf with our OSS release script should work again once
this change is merged.
This is best reviewed commit-by-commit, I tried to group changes in
logical areas.
Notable changes:
- the upgrade of third_party/protobuf submodule, the bazel protobuf
dependency itself
- upgrade of UPB dependency to 22.x (in the past, we used to always
upgrade upb to "main", but upb now has release branch as well). UPB
needs to be upgraded atomically with protobuf since there's a de-facto
circular dependency (new protobuf depends on new upb, which depends on
new protobuf for codegen).
- some protobuf and upb bazel rules are now aliases, so `
extract_metadata_from_bazel_xml.py` and `gen_upb_api_from_bazel_xml.py`
had to be modified to be able to follow aliases and reach the actual
aliased targets.
- some protobuf public headers were renamed, so especially
`src/compiler` needed to be updated to use the new headers.
- protobuf and upb now both depend on utf8_range project, so since we
bundle upb with grpc in some languages, we now have to bundle utf8_range
as well (hence changes in build for python, PHP, objC, cmake etc).
- protoc now depends on absl and utf8_range (previously protobuf had
absl dependency, but not for the codegen part), so python's
make_grpcio_tools.py required partial rewrite to be able to handle those
dependencies in the grpcio_tools build.
- many updates and fixes required for C++ distribtests (currently they
all pass, but we'll probably need to follow up, make protobuf's and
grpc's handling of dependencies more aligned and revisit the
distribtests)
- bunch of other changes mostly due to overhaul of protobuf's and upb's
internal build layout.
TODOs:
- [DONE] make sure IWYU and clang_tidy_code pass
- create a list of followups (e.g. work to reenable the few tests I had
to disable and to remove workaround I had to use)
- [DONE in cl/523706129] figure out problem(s) with internal import
---------
Co-authored-by: Craig Tiller <ctiller@google.com>
2 years ago
|
|
|
},
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
http_archive(
|
|
|
|
|
name = "build_bazel_rules_swift",
|
|
|
|
|
sha256 = "bf2861de6bf75115288468f340b0c4609cc99cc1ccc7668f0f71adfd853eedb3",
|
|
|
|
|
url = "https://github.com/bazelbuild/rules_swift/releases/download/1.7.1/rules_swift.1.7.1.tar.gz",
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
load(
|
|
|
|
|
"@build_bazel_apple_support//lib:repositories.bzl",
|
|
|
|
|
"apple_support_dependencies",
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
apple_support_dependencies()
|
|
|
|
|
|
|
|
|
|
load(
|
|
|
|
|
"@build_bazel_rules_swift//swift:repositories.bzl",
|
|
|
|
|
"swift_rules_dependencies",
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
swift_rules_dependencies()
|
|
|
|
|
|
|
|
|
|
# This loads the libpfm transitive dependency.
|
|
|
|
|
# See https://github.com/google/benchmark/pull/1520
|
|
|
|
|
load("@com_github_google_benchmark//:bazel/benchmark_deps.bzl", "benchmark_deps")
|
|
|
|
|
|
|
|
|
|
benchmark_deps()
|
|
|
|
|
|
|
|
|
|
load("@io_opentelemetry_cpp//bazel:repository.bzl", "opentelemetry_cpp_deps")
|
|
|
|
|
|
|
|
|
|
opentelemetry_cpp_deps()
|
|
|
|
|
|
|
|
|
|
load("@io_opentelemetry_cpp//bazel:extra_deps.bzl", "opentelemetry_extra_deps")
|
|
|
|
|
|
|
|
|
|
opentelemetry_extra_deps()
|
|
|
|
|
|
|
|
|
|
# TODO: Enable below once https://github.com/bazel-xcode/PodToBUILD/issues/232 is resolved
|
|
|
|
|
#
|
|
|
|
|
#http_archive(
|
|
|
|
|
# name = "rules_pods",
|
|
|
|
|
# urls = ["https://github.com/pinterest/PodToBUILD/releases/download/4.1.0-412495/PodToBUILD.zip"],
|
|
|
|
|
#)
|
|
|
|
|
#
|
|
|
|
|
#load(
|
|
|
|
|
# "@rules_pods//BazelExtensions:workspace.bzl",
|
|
|
|
|
# "new_pod_repository",
|
|
|
|
|
#)
|
|
|
|
|
#
|
|
|
|
|
#new_pod_repository(
|
|
|
|
|
# name = "CronetFramework",
|
|
|
|
|
# is_dynamic_framework = True,
|
|
|
|
|
# podspec_url = "https://raw.githubusercontent.com/CocoaPods/Specs/master/Specs/2/e/1/CronetFramework/0.0.5/CronetFramework.podspec.json",
|
|
|
|
|
# url = "https://storage.googleapis.com/grpc-precompiled-binaries/cronet/Cronet.framework-v0.0.5.zip",
|
|
|
|
|
#)
|
