bazelbuild / bazelbuild/rules_apple

Support producing static XCFrameworks that is importable from Swift

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

Description

Assuming this would fall into `framework_type = ["static"]` (not sure why this is a list) in the `apple_xcframework` rule.

In the meantime, users can use `apple_static_xcframework` with a post-process to add module map files, but note that XCFrameworks produced this way aren't usable as-is from normal Xcode Swift projects.

Contributor guide

Open the contributing guide

Research direction

Start with the apple_xcframework rule and its framework_type setting, then compare it with apple_static_xcframework. Review how the current post-process adds module map files and verify the resulting XCFramework in a normal Xcode Swift project. Done means static XCFrameworks from apple_xcframework are directly importable from Swift.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
build-system, mobile-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.