| commit | 29bbe31bb54962f3c936ae6d4c6f2cc2c203d8dd | [log] [tgz] |
|---|---|---|
| author | oquenchil <23365806+oquenchil@users.noreply.github.com> | Fri Jan 12 11:04:49 2024 +0100 |
| committer | GitHub <noreply@github.com> | Fri Jan 12 10:04:49 2024 +0000 |
| tree | efc25fd130a093b21859ee46cffdbc1696d2cd8b | |
| parent | 0cc76019401b22fca4e9aa62ef12a4f324845c29 [diff] |
Fix versioned shared libraries for macOS toolchain (#20847) The toolchain was passing -l:name. This mechanism doesn' t exist on macOS, instead the full path to the shared library should be passed. Mainline commit: https://github.com/bazelbuild/bazel/commit/f0ade80ce920be0719b1a43a40258397f68a944d As it says on that mainline commit, it cannot be checked in with a test unlike this PR, because the macOS toolchain was moved outside of Bazel. Therefore, the change must go in, the macOS toolchain needs to be updated, then the test can be added. This change does go in with a test because the toolchain is still embedded in Bazel for 6.5. Fixes https://github.com/bazelbuild/bazel/issues/20487
{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
