Swift 6.4 support#845
Draft
johnfairh wants to merge 4 commits into
Draft
Conversation
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.
Update for Swift 6.4
Few basic changes using Xcode 27b2 / swiftlang-6.4.0.23.5
Then a bigger change to deal with SwiftPM 6.4, which switches the build backend to "Swift Build".
Sadly this no longer produces the debug.yaml file that we used to get compiler arguments for SourceKit.
This PR adds an Xcode-like method for SwiftPM -- build the package with a "-v" flag, spot the command to build the module, and parse out the compiler arguments and source files.
Very little new code for this, reuses the Xcode arg-parsing routines, but moving all the SwiftPM-specific stuff into a new file, refactors in separate commits.
WIP - see how the beta train goes over the summer.