commit | 23f171e2208700dc2f2f65f5ccb32bacd7aec87d | [log] [tgz] |
---|---|---|
author | janakr <janakr@google.com> | Fri Jul 30 19:01:58 2021 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Jul 30 19:03:17 2021 -0700 |
tree | 912b071e0771db9c6f2d13dfdcb73b2edc29f20a | |
parent | a5127917b3aa0a4f64214d2203d5f0f396facb38 [diff] |
Avoid touching the filesystem to see what the BUILD file for a Starlark extension was: we already have the package, so we can just read it out. Genquery remains buggy here. haxorz@ observed in http://b/123795023#comment6 that we only need to read these paths to determine if the package was defined in a BUILD or BUILD.bazel file. Since the package already knows that, we just ask it. PiperOrigin-RevId: 387923753
{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:
See CONTRIBUTING.md