bazelbuild / bazelbuild/rules_apple

Linking error with apple_xcframework depending on each other

Open
#1,850 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Starlark
Stars
593
Forks
334
Avg merge
16h 48m
Merged PRs (30d)
9

Description

When using a `apple_xcframework` target in the `deps` of another, I get a linking error. I've seen the work from e6a22d7017813bc1825b3e5fbeb525311f4d9cf8 and thought this would fix my issue.

My workaround is currently to have a `genrule` unzip the xcframework archive, and use `apple_dynamic_xcframework_import` on the resulting files, so I'm sure there's a way to have `apple_xcframework` output the proper providers right away.

I'm up for implementing it myself but I'd need a bit of assistance.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the referenced change e6a22d7017813bc1825b3e5fbeb525311f4d9cf8 and inspecting the providers emitted by apple_xcframework when used in deps. Reproduce the linking error, then verify that direct apple_xcframework dependencies link without the genrule unzip and apple_dynamic_xcframework_import workaround.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.