Skip to content

fix: enable Universal Binary build for Intel Mac compatibility#3

Open
mazdabeam wants to merge 1 commit intoiad1tya:mainfrom
mazdabeam:fix/universal-binary-build
Open

fix: enable Universal Binary build for Intel Mac compatibility#3
mazdabeam wants to merge 1 commit intoiad1tya:mainfrom
mazdabeam:fix/universal-binary-build

Conversation

@mazdabeam
Copy link
Copy Markdown

@mazdabeam mazdabeam commented Mar 27, 2026

Summary

  • Add ARCHS = "$(ARCHS_STANDARD)" to all four build configurations (Project-level Debug/Release and Target-level Debug/Release) to produce a Universal Binary containing both arm64 (Apple Silicon) and x86_64 (Intel) slices
  • Fix invalid MACOSX_DEPLOYMENT_TARGET value 26.114.6 in Project-level Debug and Release configurations
  • Set ONLY_ACTIVE_ARCH = NO in Project Debug so all architectures are compiled even in debug builds

Verification

$ lipo -info Quitty.app/Contents/MacOS/Quitty
Architectures in the fat file: x86_64 arm64

Build confirmed with xcodebuild -project Bye.xcodeproj -scheme Quitty -configuration ReleaseBUILD SUCCEEDED

Test plan

  • xcodebuild -project Bye.xcodeproj -scheme Quitty -configuration Release completes with BUILD SUCCEEDED
  • lipo -info Quitty.app/Contents/MacOS/Quitty shows both x86_64 and arm64
  • App launches on Intel Mac (macOS 14.6+)
  • App launches on Apple Silicon Mac (macOS 14.6+)

🤖 Generated with Claude Code

Summary by Sourcery

Ensure the macOS app builds as a universal binary compatible with both Apple Silicon and Intel Macs by correcting build settings.

Enhancements:

  • Configure project and target build architectures to produce a universal binary including both arm64 and x86_64 slices.
  • Correct the macOS deployment target value in project build configurations to a valid supported version.
  • Adjust debug build settings so all architectures are compiled instead of only the active one.

- Add ARCHS = "$(ARCHS_STANDARD)" to all four build configurations
  (Project-level Debug/Release and Target-level Debug/Release)
- Fix invalid MACOSX_DEPLOYMENT_TARGET value "26.1" to "14.6" in
  Project-level Debug and Release configurations
- Set ONLY_ACTIVE_ARCH = NO in Project Debug so all architectures
  are compiled even in debug builds

Verified: xcodebuild produces a fat binary containing both
x86_64 (Intel) and arm64 (Apple Silicon) slices.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Mar 27, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Configures the Xcode project to build Quitty as a Universal Binary for both Apple Silicon and Intel Macs by adjusting architectures, deployment target, and debug build settings in the project.pbxproj.

File-Level Changes

Change Details Files
Enable Universal Binary output for the Quitty target across all configurations.
  • Set ARCHS to use ARCHS_STANDARD in project-level Debug and Release configurations.
  • Set ARCHS to use ARCHS_STANDARD in target-level Debug and Release configurations.
  • Ensure both arm64 and x86_64 slices are produced for the app binary.
Bye.xcodeproj/project.pbxproj
Correct macOS deployment target configuration for the project.
  • Replace invalid MACOSX_DEPLOYMENT_TARGET value 26.1 with 14.6 in project-level Debug configuration.
  • Replace invalid MACOSX_DEPLOYMENT_TARGET value 26.1 with 14.6 in project-level Release configuration.
  • Align deployment target with supported macOS versions for both Intel and Apple Silicon Macs.
Bye.xcodeproj/project.pbxproj
Ensure all architectures are built even in Debug.
  • Set ONLY_ACTIVE_ARCH to NO in the project Debug configuration so that all specified architectures are compiled during debug builds.
Bye.xcodeproj/project.pbxproj

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant