| commit | ca216f5eb4b1f1892219db0f578495bbbdbaa875 | [log] [tgz] |
|---|---|---|
| author | cpeyser <cpeyser@google.com> | Wed Sep 13 21:24:40 2017 +0200 |
| committer | Philipp Wollermann <philwo@google.com> | Thu Sep 14 18:46:43 2017 +0200 |
| tree | 2cd1853f5424c44dc57e986ee0bd5e3f4ad3bc50 | |
| parent | d1bd9d6637a7201e31e94683a9bc12cc59ac3651 [diff] |
Introduce empty "toolchain_category" rule for labels that will be used as categories of toolchains for the purpose of toolchain selection. Up to now, we've used the native toolchain_type rule for this purpose. That rule depends on a number of configuration fragments that supply build variables - we don't want toolchains to need to depend on those fragments as well. E.g. toolchain_type depends on JvmConfiguration, but we would like toolchains to work with --experimental_disable_jvm. PiperOrigin-RevId: 168577759
{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 system. 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.