You can make these individual targets if you want to avoid building the whole repository; the dependency tree should be properly set up for this. The other aspect as well is that the hello world example doesn't use SSL, so you can also reduce the overall list of dependencies by using the unsecure version of grpc instead as to not pull the OpenSSL / BoringSSL dependency.
Unfortunately for protobuf, you can't use protobuf-lite in the plugins, so grpc_cpp_plugin requires the full protobuf dependency. But you should indeed be able to tweak the example to use protobuf-lite instead for its own runtime. The other important dependencies we have are: zlib for the stream compression. c-ares for the DNS resolver. On Monday, August 27, 2018 at 5:23:55 AM UTC-7, Prashant Shubham wrote: > > I wanted to know what is the least number of dependencies needed for grpc. > I want reduce the size of grpc example as low as possible. It's reduce by > large if use protobuf-lite. How can I just install grpc_cpp_plugin and > grpc++, grpc++_reflection without make of the whole grpc repo. > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/f4a9f907-d5e9-4e83-bcb0-bd551389a508%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
