Locate builtins using path from flag This makes BzlLoadFunction resolve builtins bzls by reading the Root from --experimental_builtins_bzl_path, instead of doing package lookup on a hardcoded placeholder package path. Builtins bzls must now be loaded via the `@_builtins//:` syntax. The special %install_base% and %workspace% path values are not yet supported. Also: - BzlLoadFunction now takes a BlazeDirectories - @_builtins is a reserved RepositoryName - Error messages in BzlLoadFunction now signal when the failure was in a builtin Work toward #11437. PiperOrigin-RevId: 339141292
{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
