| commit | 76b3c242831f8e88835e3002a831a185a41fcc52 | [log] [tgz] |
|---|---|---|
| author | Ed Schouten <eschouten@apple.com> | Mon Nov 29 05:34:39 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Nov 29 05:36:11 2021 -0800 |
| tree | c5adf62ea25b509137fe713be38d389408a04697 | |
| parent | cd4bc7ce3d2a51ecf8df7eea7a8b3b6270357f11 [diff] |
Build xcode-locator as a universal binary One of Buildbarn's users is attempting to build it on a Mac M1 system that does not have Rosetta installed: https://github.com/buildbarn/bb-remote-execution/issues/89 This currently fails with the following error message: ERROR: <storage>/external/com_google_protobuf/BUILD:130:11: Compiling src/google/protobuf/extension_set.cc failed: I/O exception during sandboxed execution: com.google.devtools.build.lib.shell.ExecFailedException: java.io.IOException: Cannot run program "<tmp>/install/71ed47cad951a20fff87381f54639763/xcode-locator": error=86, Bad CPU type in executable Let's address this by shipping a copy of xcode-locator that is built both for ARM64 and x86-64. Closes #14168. PiperOrigin-RevId: 412864310
{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
