| commit | bd4ca0b95ff9e8c5d6c9c3741e0d4d5131df5cfa | [log] [tgz] |
|---|---|---|
| author | brandjon <brandjon@google.com> | Mon Aug 05 00:18:10 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 05 00:19:18 2019 -0700 |
| tree | acf864582787b6a004dea8168eb7b95d832f029a | |
| parent | b5a727adf655a21f094194dd8b87338092e9cd5d [diff] |
Add convention for location of standard runfiles library. hlopko@ approved this suggested convention before he left. It's consistent with what we already do in @bazel_tools. RELNOTES: None PiperOrigin-RevId: 261629882
{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.