-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add --incompatible_disable_objc_library_transition #19256
Add --incompatible_disable_objc_library_transition #19256
Conversation
Can confirm that, when flipped, this leads to clean builds both under rules_apple and under cc_binary in our teams repo's fairly large set of cc <-> objc interoperability cases, fixing #19204. Thanks, Keith! To ease the migration, might you at some point also want some of the test changes from #19236, easing assumptions on under-configured sets of internal flags? |
src/main/java/com/google/devtools/build/lib/starlarkbuildapi/cpp/CcModuleApi.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a test for the flag?
Nice, thanks! I was also looking into removing this transition. It needs some depo fixes, but not a lot of them. So once this is merges, I can look into flipping the default value. |
31fe00e
to
4497176
Compare
Added a quick test! |
This is a migration for bazelbuild#16870 Users who rely on the current behavior should instead wrap their library in a target from [rules_apple](https://github.com/bazelbuild/rules_apple).
4497176
to
67ab1b6
Compare
I hit a related issue yesterday! Thank you 🙏🏻 |
@bazelbuild/triage Is this being manually imported or does it need the label? |
@brentleyjones @comius @buildbreaker2021 if this needs to be merged to the master, then please add the label, "awaiting-PR-merge". We'll handle it afterwards. Thanks! |
Unfortunately, I don't have the ability to add labels. |
Based on your comment I just changed them. Thanks @googlewalt! |
@bazel-io flag |
@bazel-io fork 6.4.0 |
@comius @cpsauer @keith @googlewalt @buildbreaker2021 @brentleyjones
should be removed from the release-6.4.0 branch before cherry-picking
before the cherry-picking, the release branch should have above removed and instead have below:
should be removed from the release branch before cherry-picking
,
,
should be added to the release branch before cherry-picking cc: @bazelbuild/triage |
This is a migration for bazelbuild#16870 Users who rely on the current behavior should instead wrap their library in a target from [rules_apple](https://github.com/bazelbuild/rules_apple). Fixes bazelbuild#19204 Closes bazelbuild#19256. PiperOrigin-RevId: 561253613 Change-Id: I1b1b24a08caa33e86881bfe376a525060c9887a9 (cherry picked from commit 0f34e76)
This is a migration for bazelbuild#16870 Users who rely on the current behavior should instead wrap their library in a target from [rules_apple](https://github.com/bazelbuild/rules_apple). Fixes bazelbuild#19204 Closes bazelbuild#19256. PiperOrigin-RevId: 561253613 Change-Id: I1b1b24a08caa33e86881bfe376a525060c9887a9 (cherry picked from commit 0f34e76)
The changes in this PR have been included in Bazel 6.4.0 RC1. Please test out the release candidate and report any issues as soon as possible. If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=last_rc. |
This is a migration for #16870
Users who rely on the current behavior should instead wrap their library in a target from rules_apple.
Fixes #19204