commit | 0ecc30ee5e29a74edf9b8767bfa7f954f1665b9e | [log] [tgz] |
---|---|---|
author | lberki <lberki@google.com> | Wed Mar 04 09:02:57 2020 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Mar 04 09:04:21 2020 -0800 |
tree | 571a5444d3772e365198073cebb034524e90ac73 | |
parent | b20130ea6138a8e2c2e10cfbe65bd4d6f8788eba [diff] |
Create source artifacts in the ninja_build rule instead of requiring them to be explicitly listed in the ninja_build.srcs attribute. Pros: * Makes it unnecessary to duplicate information in BUILD and .ninja files * Absolves Bazel from tracking gazillions of unnecessary files Cons: * Can be problematic if multiple --package_path entries exist (e.g. one can have file a/b/c in one root while there is a/b/BUILD in another) * Invalidates the invariant that "bazel query 'deps(<target>)'" returns all files that can possibly be needed to build that target That's why Ninja support is still in experimental mode. RELNOTES: None. PiperOrigin-RevId: 298863427
{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