yonaskolb / yonaskolb/XcodeGen
Ability to support dependencies across projects
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
I'd like to have multiple Xcode projects for a mammoth iOS app. Say, MyApp.xcodeproj ThirdParty.xcodeproj Core.xcodeproj.
Currently, there is dependencies between the targets in these projects. Say, MyApp depends on ThirdParty and Core. Core depends on ThirdParty as well.
I'd like for XcodeGen to be able to partition dependencies across multiple targets within the same workspace. Is this something reasonable or in the cards for XcodeGen.
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 reviewing XcodeGen's project and workspace generation paths to understand how targets and dependencies are currently represented. Define how dependencies should be partitioned across the three example projects, then verify the behavior with coverage for cross-project dependencies and workspace generation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100