Correct headers (#209)

* Update README.md because of Bazel 0.22.0 release

- with Bazel 0.22.0, no flags are required to use rules_foreign_cc
- improve Bazel versions related information
- add link to "rules_foreign_cc take-aways"

* Correct headers in README
This commit is contained in:
irengrig 2019-01-29 14:55:29 +01:00 committed by GitHub
parent 6f0005be09
commit 0984825255
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 3 deletions

View File

@ -9,11 +9,16 @@ Rules for building C/C++ projects using foreign build systems inside Bazel proje
## Bazel versions compatibility
#####Bazel HEAD after [cae1e816e](https://github.com/bazelbuild/bazel/commit/cae1e816e5e1142fbd4aefdd29bffb2cbad71fa8) or 0.23+:
**Bazel HEAD after [cae1e816e](https://github.com/bazelbuild/bazel/commit/cae1e816e5e1142fbd4aefdd29bffb2cbad71fa8) or 0.23+:**
No flags are required, works on Windows.
#####Bazel 0.22:
**Bazel 0.22:**
No flags are required, but unfortunately Bazel's Starlark C++ API **is broken on Windows**.
#####Bazel 0.20 - 0.21:
**Bazel 0.20 - 0.21:**
Pass the Bazel the following flag:
```
--experimental_cc_skylark_api_enabled_packages=@rules_foreign_cc//tools/build_defs,tools/build_defs,@foreign_cc_impl