| commit | 6938c49616a7aa71096d6ac1c534109e0d3645e2 | [log] [tgz] |
|---|---|---|
| author | Googler <waltl@google.com> | Thu Oct 17 13:03:03 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 17 13:04:38 2024 -0700 |
| tree | d51a829d24cb878d19d367a260e2250c3caa5528 | |
| parent | 505596a45461c0e7a212c30f10db86e1e53d483b [diff] |
Deduplcate rpaths in linkopts When switching to cpp linking variables, we need to modify the Apple rules to ensure that -Wl,-rpath,/usr/lib/swift appear before other rpaths. But we still need to leave behind that rpath in swift rules for linking rules that don't use apple rules (e.g. cc_binary). The side effect is that the are now more Appler linker warning about duplicate rpaths for simple targets. I don't know of a way to turn that off, and since we already have logic to deduplicate frameworks, let's deduplicate rpaths while we're at it. PiperOrigin-RevId: 687016661 Change-Id: Iba80b5690121ba90453e461057167d0920eafa5f
{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
