| commit | 7866fd90d216d6bec7af3631ded5b2db56c5cde2 | [log] [tgz] |
|---|---|---|
| author | Keith Smiley <keithbsmiley@gmail.com> | Tue Oct 11 17:58:56 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 11 18:00:29 2022 -0700 |
| tree | 3f415565e41404a0100c19a026e4ee259336cc13 | |
| parent | c5ccb06cb40dff72c69ea774e63cb8a1eea8ea1e [diff] |
Move macOS framework name linking into framework feature This is a subtle change that moves the `-framework Foo` arguments to the linker after the `-filelist` argument. This matters in the case you have multiple symbols, one that is in your code, where the objects / archives are in the filelist, and one is in one of your pre-compiled framework dependencies. Previously the framework definition would have been preferred. This is inline with the order Xcode uses for this. The difference has cause real issues with prebuilt Swift https://github.com/apple/swift/issues/61287 Closes #16342. PiperOrigin-RevId: 480496762 Change-Id: Id5c7c839ba7b0e4323090810b8195ce6ef099eb7
{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
