| commit | 165144579b752afc2d81954f6f0eb3cb3bf1f02c | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Sat Sep 07 10:54:07 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Sat Sep 07 10:54:56 2019 -0700 |
| tree | 6178d2f4d9b8136d7356d25b69cb7bea548e18b8 | |
| parent | 458aa9e5eb4b4bb1da124deb2e41d21aa9263cde [diff] |
bazel syntax: rationalize the build rules This change adds a BUILD file to lib/syntax. The BUILD file declares two java_libraries (frontend and evaluator) that define a single Java package (lib.syntax). This unusual arrangement lets us internally structure the Java package as two parts, with dependencies in only one direction, in anticipation of splitting the Java package and renaming both halves, without affecting clients as we break dependencies one class at a time. For now, clients continue to depend on the existing lib:syntax build rule. Nearly all references to :skylark_semantics have been replaced by :syntax, except where this creates a cycle. (In all cases the client already had a dependency on :syntax.) PiperOrigin-RevId: 267782115
{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.