| commit | 34bf56f25eb1bed7fbd5c4cf7bae15bf461cf904 | [log] [tgz] |
|---|---|---|
| author | hlopko <hlopko@google.com> | Sat Feb 23 01:22:01 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Sat Feb 23 01:23:53 2019 -0800 |
| tree | 9b2a2d61ac7f82ec700676d60b61fdc49c7484d5 | |
| parent | 7567fb385ba13871ceea19bb4d2c203bd0aafc75 [diff] |
Expose is_using_fission crosstool variable for compile actions Before, per_object_debug_info_file was exposed for compilation actions, and is_using_fission for linking actions. It makes sense to have is_using_fission variable for both. I'm keeping per_object_debug_info variable there for actions that produce the .dwo file. It's important to note that not all compile actions generate .dwo, even when using fission. In case of thin_lto, we only produce the file by the backend compile actions. But for bitcode compile action we still want to enable is_using_fission. RELNOTES: is_using_fission crosstool variable is now exposed in all compile actions when fission is active (it used to be exposed only for linking actions). PiperOrigin-RevId: 235321858
{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.