| commit | 2b47bc9389361fd3b4ff70ec20d34c288c2be61d | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Fri Sep 26 09:56:26 2025 +0200 |
| committer | GitHub <noreply@github.com> | Fri Sep 26 07:56:26 2025 +0000 |
| tree | a8e1976f445e6eee43d16e1187d1d7f683d1b752 | |
| parent | c3baf305652166afdede85ea2e5fe0903b133cd9 [diff] |
[8.4.2] Remove xcode_locator's no_uuid and codesigning workarounds (#27087) These workarounds were added (in 76b3c24283, bazelbuild/bazel#14168) to enable hermetic macOS toolchain setup, but are no longer necessary as far as I can tell (see also: bazelbuild/apple_support@44c43c715a, bazelbuild/apple_support#373). It should be noted that macOS Tahoe seems to have enforced that LC_UUID must be present in executables. Executables without it are rejected by dyld with `dyld: missing LC_UUID load command`, effectively stops Bazel from working. It is therefore necessary to drop these workarounds here and in Apple support (done in bazelbuild/apple_support@44c43c715a) in order for Bazel to function on macOS Tahoe. CC @keith Closes #27014. PiperOrigin-RevId: 811436317 Change-Id: I9d819fdbc2b76ad4ee5abb1fc0c4eb1ee1b442fb Commit https://github.com/bazelbuild/bazel/commit/433e0e782c14802b6ec3095ccd5fa23b26531dea Co-authored-by: Ruoyu Zhong <zhongruoyu@outlook.com>
{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
