| commit | 52d718c11b73af6c5b278710dfce26434b2e0380 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Mon Sep 11 23:03:52 2017 +0200 |
| committer | Philipp Wollermann <philwo@google.com> | Tue Sep 12 14:05:56 2017 +0200 |
| tree | a22d669abd37ba4aa74c21c5778e98fc41b7ae54 | |
| parent | bb50580a7f3eb3f4e7c5fba8e92d20e931591a70 [diff] |
Don't attempt LTO indexing of cc_binary if there are no bitcode inputs to link. The problem is that the linker will not produce the expected .params file output if there are no inputs, and there is no need for this step in that case. This required adding a method to check if there are any bitcode inputs to the link either directly or indirectly via a library. This is the same walk done by createLtoArtifacts once we decide to do an LTO indexing step. RELNOTES: NONE PiperOrigin-RevId: 168281516
{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.