It is recommended to use CMake or automake to compile to save the trouble of dealing with dependencies. gRPC Reflection Reflection can be enabled by linking agains gRPC::grpc++reflection, enabling support for the grpccli tool. The above "-Wno-deprecated-declarations" is to eliminate the following compilation warnings: /usr/local/grpc/include/grpcpp/impl/codegen/proto_utils.h:52:32: Warning: It is not recommended to use'int google::protobuf::MessageLite::ByteSize() const' (declared in /usr/ local/grpc/include/google/protobuf/message_lite.h:402): Please use ByteSizeLong() instead īecause there are a lot of libraries, in order to avoid the pitfalls due to the order of static libraries, "–start-group" and "–end-group" are used directly to ignore the order relationship. For some background info, have a look at this blog post explaining how to structure gRPC projects with CMake. The following is an example of a Makefile: # Protobuf-Must be Protobuf3 Variables with PROTOBUF prefix are still supported for compatibility. Changed in version 3.6: All input and output variables use the Protobuf prefix. New in version 3.6: Support for findpackage () version checks. Libabsl_int128.a libabsl_strings_internal.a libgpr.a libgrpc++_error_details.a libgrpc++_unsecure.aĪmong them, cmake and pkgconfig are directories, it will be easier if you use CMake to compile. Locate and configure the Google Protocol Buffers library. Libabsl_dynamic_annotations.a libabsl_strings.a libcrypto.a libgrpc_cronet.a libgrpc_unsecure.a pkgconfig gRPC C++ itself does have dependencies on other libraries though. Libabsl_base.a libabsl_spinlock_wait.a libcares.a libgrpc++_alts.a libgrpc++_reflection.a libz.a grpc Share Improve this question Follow asked at 7:24 Anh Tran 73 1 7 I'm not sure what exactly is the problem - those instructions do actually build gRPC for C++ only - they don't build other programming language extensions. Libabsl_bad_optional_access.a libabsl_raw_logging_internal.a libaddress_sorting.a libgrpc++.a libgrpcpp_channelz.a libupb.a It has so many libraries and dependent libraries as follows: $ lsĬmake libabsl_log_severity.a libabsl_throw_delegate.a libgrpc.a libgrpc_plugin_support.a libssl.a It is not easy to write Makefile manually.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |