-
Notifications
You must be signed in to change notification settings - Fork 15.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
Add support for components when using find_package #1609
Add support for components when using find_package #1609
Conversation
Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok to test. |
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
ffcb27d
to
a3cbd1a
Compare
CLAs look good, thanks! |
a3cbd1a
to
b83e67b
Compare
77a1539
to
75a26b9
Compare
01aff14
to
d849a92
Compare
d849a92
to
e389202
Compare
e389202
to
806b173
Compare
#1654 Does a better job of solving this problem without the added complexity. |
Allow users to specify which parts of the library they want to import when issuing a find_package command.
Components are libprotobuf, libprotobuf-lite, libprotoc, and protoc. If no component is specified, all are assumed..
Fixes #1585 by allowing separate find_pacakage commands to be used for the libraries & protoc.