| commit | 2cda58fe03745baaab99e663afbdcf092c46a39e | [log] [tgz] |
|---|---|---|
| author | Keith Smiley <keithbsmiley@gmail.com> | Tue Sep 09 00:11:20 2025 +0000 |
| committer | Keith Smiley <keithbsmiley@gmail.com> | Tue Sep 09 00:17:24 2025 +0000 |
| tree | 3383de79e5341e708e985c79b37323c85ea7623a | |
| parent | be4a4eb175b0dee5d1b7ccfc452be27021533967 [diff] |
Use feature instead of cpp fragment for dSYM generation This was discussed in https://github.com/bazelbuild/bazel/pull/25881 where we believed it was equivalent. This isn't equivalent if the toolchain does not support dSYM generations but --apple_generate_dsym is still passed (as is possible on Linux). In this case we let feature configuration handle this instead, as this feature is requested when --apple_generate_dsym is passed. In that case because of this mismatch this directory will be created "successfully" but it will always be empty (this would be a failure if it wasn't a tree artifact)
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
