commit | 3c47b4716e6eca2b8ab06253915ef8d1bdd28038 | [log] [tgz] |
---|---|---|
author | Uri Baghin <uri@canva.com> | Mon Jan 23 01:56:35 2023 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 23 01:57:56 2023 -0800 |
tree | c406b17dfdddaecf1862fa0c885591df407ef71c | |
parent | de062a6750fdea75361e42f8d198c09bf6825d76 [diff] |
Find `libtool` when using `BAZEL_USE_CPP_ONLY_TOOLCHAIN`. Instead of hardcoding `/usr/bin/libtool` which requires Xcode / Xcode CLT installed, which `BAZEL_USE_CPP_ONLY_TOOLCHAIN` is meant to avoid. Related to https://github.com/bazelbuild/bazel/issues/16009. Closes #16010. PiperOrigin-RevId: 503922158 Change-Id: I64392ada951938d612dd0b28141e6b2e4ee6952c
{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