| commit | ab38960b9f34b965352d953afc00b918a97966a3 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Aug 17 05:40:27 2017 +0200 |
| committer | Irina Iancu <elenairina@google.com> | Thu Aug 17 09:54:45 2017 +0200 |
| tree | 35ec33254ef4033482bfc901a26a5c25bedaee58 | |
| parent | 5e65c9828f424b6b0214b984b5d38c9cfc1c746f [diff] |
Honor --nobuild_runfile_links for non-tests, and propagate it to the host configuration. I think the comment I'm deleting is misleading. PAR file construction already has special handling of the input manifest, and host tools do get their runfiles when executed remotely. They don't get them for local execution, but users who care about that don't need to pass the non-default --nobuild_runfile_links option. RELNOTES: None. PiperOrigin-RevId: 165535870
{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.