Create a new feature is_cc_fake_binary when the build target is a cc_fake_binary. Negative compilation test will execute build command extracted from cc_fake_binary in .runfiles directory. When xbinaryfdo is enabled through --config=release for cc_fake_binary, the build in Negative compilation test will fail because xbinaryfdo profile doesn't exist in .runfiles directory. By adding is_cc_fake_binary feature, xbinary feature will only be expanded with no feature is_cc_fake_binary existing. Tested: new_blaze test javatests/com/google/devtools/build/lib/rules/... new_blaze test third_party/bazel/src/main/java/com/google/devtools/... RELNOTES: None. PiperOrigin-RevId: 222473523
{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.