yonaskolb / yonaskolb/XcodeGen
unnecessary build Action entry is added for all schemes
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 had an issue using XcodeGen which is a new build entry action that should not be there comparing to the base xcconfig setting!!!
Before XcodeGen generate
<BuildActionEntries>
<BuildActionEntry
buildForTesting = "YES"
buildForRunning = "YES"
buildForProfiling = "YES"
buildForArchiving = "YES"
buildForAnalyzing = "YES">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "469429DBC0D995EDA2C2DA26"
BuildableName = "####.app"
BlueprintName = "#####"
ReferencedContainer = "container:#####.xcodeproj">
</BuildableReference>
</BuildActionEntry>
</BuildActionEntries>
After
<BuildActionEntries>
<BuildActionEntry
buildForTesting = "YES"
buildForRunning = "YES"
buildForProfiling = "YES"
buildForArchiving = "YES"
buildForAnalyzing = "YES">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "469429DBC0D995EDA2C2DA26"
BuildableName = "####.app"
BlueprintName = "####"
ReferencedContainer = "container:####.xcodeproj">
</BuildableReference>
</BuildActionEntry>
<BuildActionEntry
buildForTesting = "YES"
buildForRunning = "NO"
buildForProfiling = "NO"
buildForArchiving = "NO"
buildForAnalyzing = "NO">
<BuildableReference
BuildableIdentifier = "primary"
BlueprintIdentifier = "FF626AA8556AA311B770465C"
BuildableName = "#####.xctest"
BlueprintName = "####Tests"
ReferencedContainer = "container:####.xcodeproj">
</BuildableReference>
</BuildActionEntry>
</BuildActionEntries>
Have you an idea about this issue please?
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 names no source files, tests, or entry points. Reproduce the generated Xcode scheme from the before-and-after snippets, then trace how XcodeGen creates scheme build action entries and compares them with the base xcconfig settings. Done means generated schemes no longer contain the unnecessary entry for schemes where it is not configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100