| commit | 4843f29a445761c31761152ab4e7d4cad9c346d2 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri Jun 03 15:56:37 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 03 15:58:19 2022 -0700 |
| tree | 31e1941dabb95e1a023d5674104ddb89d6ceb2df | |
| parent | 3b8960c7f4e53267997cdff452c26fe1efea1651 [diff] |
Fix up genrule documentation
- Remove a passage in the documentation of `cmd` that made reference to a concept that was previously removed from the documentation ("Note that outs are not included in this substitution"). "this substitution" originally referred to heuristic label expansion (see unknown commit), but the mention of heuristic label expansion was removed (unknown commit), leaving the sentence appearing to refer to `$(location)` substitution, but `outs` are indeed included in that substitution.
- Add some detail to `outs` documentation about how `cmd` should reference output paths (partially copied from the passage removed per the point above).
- Remove a passage about referring to *_binary targets in `cmd`; it feels both redundant and incomplete and seems generally unhelpful. The information it provides is expressed more clearly elsewhere.
- Fix links to `$(location)` substitution details (anchor is now #predefined_label_variables)
PiperOrigin-RevId: 452860438
Change-Id: I4a061923548b0b3279e7c8038469d9ca66babd9f
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only 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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
