When filtering out undeclared headers during input discovery, do so right in the include scanner. Filtering them out retroactively can lead to incorrect results, e.g. in a situation like this: a.h -> b.h -> c.h If b.h is an existing file, but not a dependency of a.h, but c.h is, then the retroactive filtering can filter out b.h, but will not remove c.h. This is can lead to inefficiencies and unexpected results. RELNOTES: None. PiperOrigin-RevId: 343155457
{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
