commit | 464a97cccaab02ec007e7c51e178569b8430edc2 | [log] [tgz] |
---|---|---|
author | djasper <djasper@google.com> | Mon Nov 16 01:54:41 2020 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Nov 16 01:55:52 2020 -0800 |
tree | 9552bc0c89b2314ba55d37bff3c180b4d95e3a51 | |
parent | 7573ff9a5c1b7bfd4b743952539c724b47415a84 [diff] |
Fix/improve handling of .d files in compile action templates. These currently don't respect settings around when to use .d files. This needs to be done in two steps, when the compile action template is created, we can avoid creating the entire tree artifact for the .d files if the configuration tells us that .d files should not be used. In addition, we can selectively disable .d files for individual inputs if the input file type isn't one that we use .d files for. RELNOTES: None. PiperOrigin-RevId: 342589186
{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