Stop losing compiler arguments for headers, symlinks and CLI builds - #312
Merged
Conversation
sourceKitOptions returned nothing for a `.h` (no build phase lists one) and for any path spelled through a symlink or a `..` segment, so a header now answers from the source beside it and file matching falls back to the standardized spelling. On Xcode 26 `xcodebuild` writes the build's `.xcactivitylog` only when `-resultBundlePath` is passed — the extension does, the CLI did not, and without that log xcode-build-server has no arguments for any file. The built-in server's docs also claimed `.xcworkspace` and Swift packages fall back to xcode-build-server, which is wrong in both cases.
hyzyla
force-pushed
the
bsp-headers-paths-build-log
branch
from
August 9, 2026 19:33
769738a to
b4c886c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sourceKitOptions returned nothing for a
.h(no build phase lists one) and for any path spelled through a symlink or a..segment; a header now answers from the source beside it, and file matching falls back to the standardized spelling. On Xcode 26xcodebuildwrites the build's.xcactivitylogonly when-resultBundlePathis passed — the extension does, the CLI did not, and without that log xcode-build-server has no compiler arguments for any file. Also corrects the docs claim that.xcworkspaceand Swift packages fall back to xcode-build-server.🤖 Generated with Claude Code
https://claude.ai/code/session_01FPVutGcKGcyTD2rJFjAyhS