yonaskolb / yonaskolb/XcodeGen
transitivelyLinkDependencies and app extensions
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
We have transitivelyLinkDependencies set to true. When adding framework dependencies to an extension, in Xcode we see that the app itself has those same frameworks as dependencies. The final app binary ends up linking to frameworks it doesn't use. Is this intended? My initial thought is that transitivelyLinkDependencies should not propagate dependencies of app extensions.
Let me know if there is more details/context I should provide.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how transitivelyLinkDependencies handles framework dependencies for app extensions and the containing app. Reproduce the described Xcode project setup and determine whether extension-only frameworks are added to the final app binary. Done means the intended propagation behavior is established and verified for app extensions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100