Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flip --incompatible_objc_linking_info_migration back for now #1813

Merged

Conversation

thii
Copy link
Member

@thii thii commented Jan 26, 2023

Fixes our builds with last_green bazel.

bazelbuild/bazel@7b4acfe

@thii thii force-pushed the thi/flip-incompatible_objc_linking_info_migration-back-for-now branch 2 times, most recently from cd83173 to 03155cf Compare January 26, 2023 14:25
brentleyjones referenced this pull request in bazelbuild/bazel Jan 26, 2023
See #16939.

This flips the default behavior so that builtin Objective C rules will get their
linking info from CcInfo instead of ObjcProvider.  We will start cleaning up
apple/swift starlark rules to stop generating linking info in ObjcProvider, so
it makes sense to flip the default for this flag before those changes land in
open source.

RELNOTES[inc]: builtin objc rules will get their linking info from CcInfo, not ObjcProvider

PiperOrigin-RevId: 504621116
Change-Id: I78ab2d3aca85dc0c7ef754dc8240ffa6a8f66ab9
.bazelrc Outdated Show resolved Hide resolved
@thii thii force-pushed the thi/flip-incompatible_objc_linking_info_migration-back-for-now branch from 03155cf to cd83173 Compare January 26, 2023 15:23
@thii thii marked this pull request as ready for review January 26, 2023 15:54
@thii thii enabled auto-merge (squash) January 26, 2023 15:55
@thii thii requested a review from brentleyjones January 26, 2023 15:56
@thii thii merged commit a60aaf8 into master Jan 27, 2023
@thii thii deleted the thi/flip-incompatible_objc_linking_info_migration-back-for-now branch January 27, 2023 01:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants