yonaskolb / yonaskolb/XcodeGen
How to have a build settings defined in "base", while customising it further in "config/Release"?
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 8.8k
- Forks
- 908
- Avg merge
- 17d 14h
- Merged PRs (30d)
- 2
Description
Hi 👋
I have the following spec:
...
settings:
base:
OTHER_SWIFT_FLAGS:
- -Xfrontend
- -warn-long-expression-type-checking=500
- -Xfrontend
- -warn-long-function-bodies=1000
configs:
Release:
OTHER_SWIFT_FLAGS:
- -Xfrontend
- -internalize-at-link
...
The intended behaviour is that:
- For all configurations,
OTHER_SWIFT_FLAGShas a value of-Xfrontend -warn-long-expression-type-checking=500 -Xfrontend -warn-long-function-bodies=1000 - For release configuration,
OTHER_SWIFT_FLAGShas a value of-Xfrontend -warn-long-expression-type-checking=500 -Xfrontend -warn-long-function-bodies=1000 -Xfrontend -internalize-at-link
The reality (which is somewhat expected) is that:
- For all configurations,
OTHER_SWIFT_FLAGShas a value of-Xfrontend -warn-long-expression-type-checking=500 -Xfrontend -warn-long-function-bodies=1000 - For release configuration,
OTHER_SWIFT_FLAGShas a value of-Xfrontend -internalize-at-link
Is there any way to achieve the intended behaviour?
Thanks! 🙏
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
The issue provides no repository file or test path. Start by tracing how the YAML settings.base and configs.Release values are parsed and merged, then verify the behavior with a minimal spec; done means Release retains base OTHER_SWIFT_FLAGS and appends its own flags while other configurations remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift, yaml
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100