MobileNativeFoundation / MobileNativeFoundation/rules_xcodeproj
Feature Request: Support mixed-architecture consolidated targets
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 626
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Currently if both an arm64 and x86_64 version of a macOS target exists in the project, they will be distinct Xcode targets. This is because certain Xcode build settings that we set can't be conditioned on arch. This doesn't affect normal Xcode projects because they don't require per-arch specific paths for outputs.
One solution that might work is finding a way to use the intermediate output directory for outputs. Those are able to use arch in their paths, and probably conditionals as well.
Another solution (which we could still do even if we did the previous) is that for BwB mode we stop changing the output folder structure, since we don't copy anything but the final bundles there.
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 files, tests, or entry points. Compare the proposed intermediate-output-directory approach with leaving the BwB output folder structure unchanged, focusing on architecture-conditioned paths and consolidated macOS targets. Done should mean arm64 and x86_64 targets can share a consolidated Xcode target without conflicting output paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100