Skip to content

Remove propagating cc libs with objc provider#420

Closed
keith wants to merge 1 commit intobazelbuild:masterfrom
keith:ks/remove-propagating-cc-libs-with-objc-provider
Closed

Remove propagating cc libs with objc provider#420
keith wants to merge 1 commit intobazelbuild:masterfrom
keith:ks/remove-propagating-cc-libs-with-objc-provider

Conversation

@keith
Copy link
Member

@keith keith commented Apr 22, 2020

When using a rule tree like this:

ios_static_framework
swift_library
objc_library
cc_library

Including these libraries in the objc provider leads them to being
included twice in the produced static binary. It appears the comment
here was outdated and that apple_binary does collect libraries directly
from the CcInfo.

When using a rule tree like this:

```
ios_static_framework
swift_library
objc_library
cc_library
```

Including these libraries in the objc provider leads them to being
included twice in the produced static binary. It appears the comment
here was outdated and that apple_binary does collect libraries directly
from the CcInfo
@keith keith force-pushed the ks/remove-propagating-cc-libs-with-objc-provider branch from 43f6cd2 to 9228117 Compare April 23, 2020 15:28
@keith
Copy link
Member Author

keith commented Apr 24, 2020

This breaks other cases where you have more objc libs that depend on the swift libs, now tracking this issue in bazelbuild/bazel#11223

@keith keith closed this Apr 24, 2020
@keith keith deleted the ks/remove-propagating-cc-libs-with-objc-provider branch April 24, 2020 23:41
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.

2 participants