Skip to content
This repository has been archived by the owner on Oct 4, 2023. It is now read-only.

Update Bazel CC-using rules to use the toolchain transition. #211

Merged

Conversation

keith
Copy link
Member

@keith keith commented Jan 7, 2021

This is phase 2 of of the switch to toolchain transitions. See bazelbuild/bazel#11584 for details.

PiperOrigin-RevId: 338462410
(cherry picked from commit 06d3ebf)

This is phase 2 of of the switch to toolchain transitions. See bazelbuild/bazel#11584 for details.

PiperOrigin-RevId: 338462410
(cherry picked from commit 06d3ebf)
@google-cla
Copy link

google-cla bot commented Jan 7, 2021

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.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added the cla: no label Jan 7, 2021
keith referenced this pull request Jan 7, 2021
This is phase 2 of of the switch to toolchain transitions. See bazelbuild/bazel#11584 for details.

PiperOrigin-RevId: 338462410
@keith keith marked this pull request as ready for review January 7, 2021 18:18
@keith keith merged commit 5920c54 into master Jan 7, 2021
@keith keith deleted the ks/update-bazel-cc-using-rules-to-use-the-toolchain-transition branch January 7, 2021 18:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant