make install fails with Xcode 27: universal build output moved from .build/apple/Products/Release to .build/out/Products/Release
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 4.8k
- Forks
- 182
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 1
Description
Installing xcodes 2.1.0 from source (both the homebrew-core formula and the xcodesorg/made tap, which run make install) fails on macOS 26.6 with Xcode 27.0 (27A266a):
Build complete! (68.59 sec)
install: .../.build/apple/Products/Release/xcodes: No such file or directory
make: *** [install] Error 71
The Makefile hardcodes RELEASEBUILDDIR = $(BUILDDIR)/apple/Products/Release/xcodes, but Xcode 27's SwiftPM emits multi-arch products under $(BUILDDIR)/out/Products/Release/ instead. The binary is built fine (universal arm64+x86_64, verified with file) — only the install path lookup fails. The sign, zip, and bottle targets are affected too.
Possible fix: resolve the path via swift build --show-bin-path instead of hardcoding it, or check both locations.
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 in the Makefile at RELEASEBUILDDIR and compare it with the path returned by swift build --show-bin-path. Check the install, sign, zip, and bottle targets, then verify that they locate the universal xcodes binary under Xcode 27. Done means make install succeeds without the hardcoded-path error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, swift
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100