| commit | e8547351f7f840950f0d7309bfba99783c57b31e | [log] [tgz] |
|---|---|---|
| author | Googler <waltl@google.com> | Thu Oct 06 20:19:29 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 06 20:20:59 2022 -0700 |
| tree | 2d43ee79c5ae3409ae8ca48e3ca69866ac0b6dd6 | |
| parent | f0085dd8b8a2f57daa9c9e98d62fa1ddd90bb069 [diff] |
In objc_library, use CcLinkingContext from build actions instead of build one from scratch This change does the following: - in objc_library, use CcLinkingContext from build actions instead of build one from scratch. - propagate CcLinkingContext in j2objc_library. - get rid of linkstamp info in ObjcProvider, which was only there to work around the fact taht objc_library's CcLinkingContext did not correctly propagate the CcLinkingContexts of its dependencies. In internal benchmarking, this reduces bazel memory usage by 3.6%. PiperOrigin-RevId: 479478548 Change-Id: I6694419b0c290cfddd845eecdf6e2a4b0294efa5
{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
