Allow starlark rules to be build settings. For skylark rules that are declared build settings, we auto-add a nonconfigurable build_setting_default attribute which must be set on a per target basis. We also add access to the build setting value via the rule context object. All of this functionality is hidden behind the --experimental_build_setting_api flag which by default is flipped off. This includes: - Add a build_setting parameter to starlark rule construction. - If a starlark rule sets the build_setting parameter, auto-add a mandatory 'build_setting_default' attribute of the same type. - Allow the value of a build setting skylark rules to be accessed via ctx.build_setting_value. - Get rid of BuildSettingDescriptor since we don't need both it and BuildSetting. - Add the --experimental_build_setting_api flag to SkylarkSemantics flags. Work towards issue #5577 PiperOrigin-RevId: 219537101
{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.