-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Expose grpc++_binder through grpc++ #27891
Expose grpc++_binder through grpc++ #27891
Conversation
A config is added so we can disable it if needed
3e133e1
to
f3e72c1
Compare
Rebase and resolved merge conflict. Now this exposes through Will double check copybara import and size impact. Will merge if they look fine |
Retrigger CI. xds test failed for some reason |
Not everyone who build shared library is using bazel so we need to provide this option to disable binder transport code.
6d66959
to
7c8bb7b
Compare
Add a new commit that allows users to disable binder transport by defining |
Can confirm that the shared library does not have any size increase after |
As discussed in the meeting, this is probably a better way to expose the code.
This should not affect binary size as long as user does not include binder headers and they are static linking.
A config option is provided so user can pass
--define=grpc_no_binder=true
to bazel to disable the dependency.A copybara import was created to dry run this change, and it looks fine