yonaskolb / yonaskolb/XcodeGen
Support bundling directory in copy bundle resources
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
The following resources
Resources/file1.txt
Resources/file2.txt
will be bundled in the app bundle as:
MyApp.app/file1.txt
MyApp.app/file2.txt
Is there any way to specify the resources to be bundled as the following? Xcode supports it if you drag the whole directory into the Copy Bundle Resources build phase.
MyApp.app/Resources/file1.txt
MyApp.app/Resources/file2.txt
Currently there's a workaround for that by adding an arbitrary extension to the resource directory (e.g. Resources.mybundle), so XcodeGen will think that it is a file.
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 XcodeGen's handling of resources in the Copy Bundle Resources build phase and compare file resources with directory resources. The requested behavior is to preserve the Resources directory inside the app bundle, while retaining existing file bundling and avoiding the arbitrary-extension workaround; add or update coverage for that behavior if the relevant test area is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100