| commit | a3c30bfdea05695578420870a725339f0b194734 | [log] [tgz] |
|---|---|---|
| author | AlexTereshenkov <50622389+AlexTereshenkov@users.noreply.github.com> | Mon Oct 09 00:14:01 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 09 00:15:47 2023 -0700 |
| tree | ecd1f4bf5d170c9c395af5719663c5614bacb455 | |
| parent | 0684fa8a44e966efb6c3421982c3b030f16de652 [diff] |
docs: extend docs for general rule (alias)
Fixing typo in markdown URL and extending the docs on why the `alias` rule may be helpful. I felt it may not be clear how this rule can be useful (based on the description and code example provided).
I was thinking to provide an example of how a `select` could have been used in an alias (i.e. it's convenient to be able to refer to a target by a single label):
```
alias(
name = "rustfmt_bin",
actual = select({
"@rules_rust//rust/platform:osx": "@rust_darwin_x86_64__x86_64-apple-darwin_tools//:rustfmt_bin",
"@rules_rust//rust/platform:linux": "@rust_linux_x86_64__x86_64-unknown-linux-gnu_tools//:rustfmt_bin",
}),
)
```
but felt this may be too detailed for the reference docs.
Closes #19763.
PiperOrigin-RevId: 571851166
Change-Id: If647507803f0c94e0e6b49363caa68e73c574338
{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
