commit | c32e4b29cf50fe7675fc19af836f6b4bca6f7b3b | [log] [tgz] |
---|---|---|
author | Greg Estren <gregestren@gmail.com> | Thu Apr 25 15:18:12 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 25 15:19:23 2019 -0700 |
tree | bdeb937d2cfcc13ce966f3a70dd104df775cbf5f | |
parent | 00a2c9e052b96fe1b1a27f838969284337aa494f [diff] |
Clarify why `cfg` is mandatory for `executable=True` attributes. I was originally considering removing `cfg = "target"` support in the name of API cleanup, since that's a semantic no-op. But the reasoning is fair for when `cfg` is mandatory (shared in a Google doc by @laurentlb): > "When an input is executable, we often want to run it on the host. So I suggest that cfg is mandatory when input is executable". But I don't think we should set `cfg = "target"` casually when it's not helpful - that'll just litter code bases. I tried to address these issues in this PR. Also note, for posterity, that `cfg = "host"` is due for deprecation: https://github.com/bazelbuild/proposals/blob/master/designs/2019-02-12-execution-transitions.md Closes #8025. PiperOrigin-RevId: 245316460
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.