Skip to content

Resolve system SDK path via xcrun in explicit-modules scan - #1902

Merged
aaronsky merged 1 commit into
bazelbuild:mainfrom
ma-oli:resolve-sdk-path-via-xcrun
Sep 16, 2026
Merged

aaronsky merged 1 commit into
bazelbuild:mainfrom
ma-oli:resolve-sdk-path-via-xcrun

Conversation

@ma-oli

@ma-oli ma-oli commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

The scanner assumed an unversioned SDK symlink (e.g. MacOSX.sdk) exists under each platform's SDKs directory. That symlink is not guaranteed to be present in every Xcode layout, causing scanning to fail with FileNotFoundError.

Ask xcrun for the resolved SDK path instead, failing loudly if it cannot be determined.

The scanner assumed an unversioned SDK symlink (e.g. MacOSX.sdk) exists
under each platform's SDKs directory. That symlink is not guaranteed to
be present in every Xcode layout, causing scanning to fail with
FileNotFoundError.

Ask xcrun for the resolved SDK path instead, failing loudly if it cannot
be determined.
@aaronsky
aaronsky merged commit 2475ea6 into bazelbuild:main Sep 16, 2026
16 checks passed
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.

2 participants