Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update reference to rules_cc to main.zip. This is required by https://github.com/bazelbuild/rules_cc/issues/107 #1603

Merged
merged 1 commit into from
Jul 1, 2021
Merged

Update reference to rules_cc to main.zip. This is required by https://github.com/bazelbuild/rules_cc/issues/107 #1603

merged 1 commit into from
Jul 1, 2021

Commits on Jul 1, 2021

  1. Update reference to rules_cc to main.zip. This is required by bazelbu… 

    …ild/rules_cc#107

The longer term solution is:
- To use a named release of rules_cc once that is available (See bazelbuild/rules_cc#91)
- Wrap the `http_archive` rules with `maybe` so that there will not be conflicts if downstream users try to mix rules_cc versions.

PiperOrigin-RevId: 382531776
    @xnnpack-bot
    xnnpack-bot committed Jul 1, 2021
    Configuration menu
    Copy the full SHA
    e1c7fed View commit details
    Browse the repository at this point in the history