XcodesOrg / XcodesOrg/homebrew-made

brew install xcodes fails on macOS 27 — Makefile hardcodes .build/apple/Products/Release, but the Swift toolchain now builds to .build/out/Products/Release

Open Beginner friendly
#4 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Environment:

  • macOS 27.0 (BuildVersion 26A428)
  • Xcode Command Line Tools with Apple clang 21.0.0 (clang-2100.3.34.2)
  • Architecture: arm64 (Apple Silicon)
  • xcodes formula version 2.1.0, installed from the xcodesorg/made tap

Problem:

brew install xcodesorg/made/xcodes fails at the install step even though the build itself completes successfully:

Build complete! (15,65 secs)
install: /private/tmp/.../xcodes-.../.build/apple/Products/Release/xcodes: No such file or directory
make: *** [install] Error 71

Also noticed this build warning, which may be related:

warning: The x86_64 architecture is deprecated for your deployment target (macOS 27.0). You should update your ARCHS build setting to remove the x86_64 architecture.

Root cause:

The Makefile's RELEASEBUILDDIR is hardcoded to:
RELEASEBUILDDIR = $(BUILDDIR)/apple/Products/Release/xcodes

But with this toolchain, swift build --arch arm64 --arch x86_64 --build-path .build actually places the multi-arch release binary at:
.build/out/Products/Release/xcodes

The .build/apple/... path used to be correct on older Swift toolchains but no longer matches — make install (and make sign/bottle/zip) can't find the binary.

Workaround that fixes it:

Patching the Makefile path before make install runs resolves it cleanly:
RELEASEBUILDDIR = $(BUILDDIR)/out/Products/Release/xcodes

After that change, make install succeeds and produces a working universal (arm64/x86_64) binary.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Makefile at RELEASEBUILDDIR and compare it with the path produced by the reported swift build command. Update the release path, then run make install and verify that the universal arm64/x86_64 binary is produced; check the related make sign, bottle, and zip targets as well.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
88/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.