Esun Kim
decc199ca8
|
4 years ago | |
---|---|---|
.. | ||
README.md | 4 years ago | |
atm.h | 7 years ago | |
atm_gcc_atomic.h | 7 years ago | |
atm_gcc_sync.h | 6 years ago | |
atm_windows.h | 4 years ago | |
byte_buffer.h | 4 years ago | |
byte_buffer_reader.h | 5 years ago | |
compression_types.h | 6 years ago | |
connectivity_state.h | 7 years ago | |
fork.h | 7 years ago | |
gpr_slice.h | 8 years ago | |
gpr_types.h | 6 years ago | |
grpc_types.h | 4 years ago | |
log.h | 4 years ago | |
port_platform.h | 4 years ago | |
propagation_bits.h | 8 years ago | |
slice.h | 6 years ago | |
status.h | 6 years ago | |
sync.h | 5 years ago | |
sync_abseil.h | 5 years ago | |
sync_custom.h | 7 years ago | |
sync_generic.h | 5 years ago | |
sync_posix.h | 6 years ago | |
sync_windows.h | 4 years ago |
README.md
Welcome to include/grpc/impl/codegen
Why is this directory here?
This directory exists so that generated C++ code can include selected files upon
which it depends without having to depend on the entire gRPC C++ library. This
directory thus exists to support include/grpcpp/impl/codegen
. This constraint
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. C++ 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 the gRPC C++ library no longer has a need for an
impl/codegen
directory of its own).