-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
grpc library bloat #187
Comments
This is likely caused by how I am building grpc (which is required since we need a later version than what is available with TOSS (if I remember correctly)). I am hoping that I can build a much liter version of grpc since I would find it hard to believe we need everything+kitchensink |
Which version is TOSS using? |
I actually do not know. It is possible that it isn't even installed on rzadams. It has been so long since we last checked. @behlendorf might be able to say which version is there (if any at all). |
Here is how I currently am building gRPC and nnfdm
|
Actually, I think that gRPC for C++ requires manual installation (at least according to https://grpc.io/blog/installation/) |
I have spent the last week or so attempting to build one of our production codes with our new SCR checkpoint library that makes use of the nnfdm.a library and have run in to some issues that I think could be a pain point for some of our code teams (thus far, I am still unable to successfully build). Library bloat. More specifically, because the nnfdm api is using grpc with protobuf, this is causing us to link in 57 (not an exaggeration) additional libraries (shown below).
Does anyone know of a lighter weight way to trim down the large number of libraries? With our codes that have complicated build systems, it is not a trivial task to deal handle the larger set of libraries that seem to be required.
The text was updated successfully, but these errors were encountered: