premake / premake/premake-core
xcodebuildresources doesn't respect folder structure
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
Description
Specifying files via xcodebuildresources doesn't appear to respect the folder structure. For example:
Real path:
shaders/
- vertex.vert
- fragment.frag
Virtual path:
Resources/
- shaders/
- vertex.vert
- fragment.frag
Adding the following to the Premake scripts:
xcodebuildresources {
"shaders",
}
Results in the files being bundled, but in the root directory rather than the shaders directory. I'm not 100% sure how XCode handles it, I tried to replicate the project configuration with Premake but the xcodeproj file was "corrupt" and wouldn't load.
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 at the xcodebuildresources entry point in the Premake scripts and inspect the generated xcodeproj configuration for the resource path. Reproduce the shaders example, then verify that vertex.vert and fragment.frag remain under Resources/shaders rather than the bundle root; done when the generated project loads and preserves that layout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100