commit | a4e7a7a5235f415eea5515b49121ec79a95b78ad | [log] [tgz] |
---|---|---|
author | lberki <lberki@google.com> | Wed Aug 21 04:37:11 2019 -0700 |
committer | John Cater <jcater@google.com> | Wed Aug 21 10:06:39 2019 -0400 |
tree | 64479780712ddef044f6e8d9496bb8c21c376f62 | |
parent | ad9f7608230dade9d00f694cfad903684dbcc627 [diff] |
Revert back to the old behavior of not creating a proto source root for generated .proto files. It was meant to be a compatible change, but alas, people seemed to depend on the exact layout of the output tree. Will flip in 1.0 . Tracking bug: https://github.com/bazelbuild/bazel/issues/9215 RELNOTES: None. PiperOrigin-RevId: 264581654
{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.