Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
[Bazel] Add support for compatible_with and restricted_to #5681
Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
These attributes have been available in Bazel for years. Pass them through so the flatbuffer rules can be used with them. They let you constrain which target platform is used. While we are here, fix gen_reflections to work with bazel.
AustinSchuh
force-pushed the
AustinSchuh:austin/compatible_with
branch
from
ba9f442
to
bd4d3fb
|
CLAs look good, thanks! |
|
Thanks! |
* Add support for compatible_with and restricted_to These attributes have been available in Bazel for years. Pass them through so the flatbuffer rules can be used with them. They let you constrain which target platform is used. While we are here, fix gen_reflections to work with bazel. * Add docs
These attributes have been available in Bazel for years. Pass them
through so the flatbuffer rules can be used with them. They let you
constrain which target platform is used.
While we are here, fix gen_reflections to work with bazel.