Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 8fec86d40eff362d8e510c24faedadb4e82bddf2
https://github.com/WebKit/WebKit/commit/8fec86d40eff362d8e510c24faedadb4e82bddf2
Author: Elliott Williams <[email protected]>
Date: 2026-01-09 (Fri, 09 Jan 2026)
Changed paths:
A Configurations/DeploymentTargets.xcconfig
A Configurations/Makefile
M Configurations/SDKVariant.xcconfig
A Configurations/Scripts/generate-deployment-target-xcconfig.py
Log Message:
-----------
[Xcode] Set MACOSX_DEPLOYMENT_TARGET to match the system version
https://bugs.webkit.org/show_bug.cgi?id=252783
rdar://105812206
Reviewed by Alexey Proskuryakov.
A common workflow for investigating downlevel bugs is to build and debug
directly on the downlevel machine. As part of back-deployment, we
require building with a modern Xcode version on downlevel machines, so
for this workflow to continue building correctly, we need to customize
the deployment target and can no longer always deploy to the SDK
version.
Change the default MACOSX_DEPLOYMENT_TARGET in at-desk builds to match
the host OS.
Separately, when using an older SDK + Xcode to build on a newer host OS,
retain the existing behvaior and deploy to the SDK version. Effectively,
we set:
MACOSX_DEPLOYMENT_TARGET = min(SDK version, Host OS version)
This also fixes a common complaint from open source WebKit developers,
where an auto-update to Xcode forces them to upgrade their OS to
continue development.
There is unfortunately no way to use XCBuild to natively convert the
MAC_OS_X_VERSION_MINOR integer to a semantic version number, so add a
script that generates a mapping table.
* Configurations/DeploymentTargets.xcconfig: Added.
* Configurations/Makefile: Added.
* Configurations/SDKVariant.xcconfig:
* Configurations/Scripts/generate-deployment-target-xcconfig.py: Added.
Canonical link: https://commits.webkit.org/305389@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
