bazelbuild / bazelbuild/rules_apple
Validate prebuilt framework library types
Open
- Dominant language
- Starlark
- Stars
- 593
- Forks
- 334
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 9
Description
It's possible to incorrectly wrap static frameworks with the `apple_dynamic_xcframework_import` rule. This _can_ compile but present headaches with downstream issues. It would be nice if we could validate that imported frameworks match the expected library type (`ar archive` vs `dylib)`
Contributor guide
Research direction
Start at the apple_dynamic_xcframework_import rule and trace how imported framework library types are currently handled. Add validation that distinguishes an ar archive from a dylib, then verify that static frameworks cannot be wrapped with the dynamic import rule.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100