0f1afec5a8
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> |
||
|---|---|---|
| .. | ||
| security | ||
| README.md | ||
| async_generic_service.h | ||
| async_stream.h | ||
| async_unary_call.h | ||
| byte_buffer.h | ||
| call.h | ||
| call_hook.h | ||
| call_op_set.h | ||
| call_op_set_interface.h | ||
| callback_common.h | ||
| channel_interface.h | ||
| client_callback.h | ||
| client_context.h | ||
| client_interceptor.h | ||
| client_unary_call.h | ||
| completion_queue.h | ||
| completion_queue_tag.h | ||
| config.h | ||
| config_protobuf.h | ||
| create_auth_context.h | ||
| delegating_channel.h | ||
| intercepted_channel.h | ||
| interceptor.h | ||
| interceptor_common.h | ||
| message_allocator.h | ||
| metadata_map.h | ||
| method_handler.h | ||
| method_handler_impl.h | ||
| proto_buffer_reader.h | ||
| proto_buffer_writer.h | ||
| proto_utils.h | ||
| rpc_method.h | ||
| rpc_service_method.h | ||
| serialization_traits.h | ||
| server_callback.h | ||
| server_callback_handlers.h | ||
| server_context.h | ||
| server_interceptor.h | ||
| server_interface.h | ||
| service_type.h | ||
| slice.h | ||
| status.h | ||
| status_code_enum.h | ||
| string_ref.h | ||
| stub_options.h | ||
| sync.h | ||
| sync_stream.h | ||
| time.h | ||
README.md
Welcome to include/grpcpp/impl/codegen
Why is this directory here?
This directory exists so that generated code can include selected files upon
which it depends without having to depend on the entire gRPC C++ library. This
is particularly relevant for users of bazel, particularly if they use the
multi-lingual proto_library target type. Generated code that uses this target
only depends on the gRPC C++ targets associated with these header files, not the
entire gRPC C++ codebase since that would make the build time of these types of
targets excessively large (particularly when they are not even C++ specific).
What should user code do?
User code should not include anything from this directory. Only generated code
and gRPC library code should include contents from this directory. User code
should instead include contents from the main grpcpp directory or its
accessible subcomponents like grpcpp/support. It is possible that we may
remove this directory altogether if the motivations for its existence are no
longer strong enough (e.g., if most users migrate away from the proto_library
target type or if the additional overhead of depending on gRPC C++ is not high).