-
Notifications
You must be signed in to change notification settings - Fork 10.5k
SwiftSyntax: some basic changes needed for Linux support #18638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
CC: @harlanhaskins |
@swift-ci please test |
.appendingPathComponent("swiftc") | ||
.deletingLastPathComponent(); | ||
#if !os(macOS) | ||
swiftcURL = swiftcURL.deletingLastPathComponent(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: no semicolon here or on line 159
@@ -48,46 +48,53 @@ struct ProcessResult { | |||
} | |||
} | |||
|
|||
@inline(__always) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this needs to be @inline(__always)
.
Small nitpicks, but thank you for tackling this! |
This adds a couple of changes to support building SwiftSyntax without an ObjC runtime as well as swift-corelibs-foundation instead of the ObjC Foundation implemetation. This is needed to support building SwiftSyntax on Linux.
114c692
to
a4c604f
Compare
@swift-ci please test |
Build failed |
Build failed |
This is soon going to conflict with #18673 |
Okay, since this is ready, I'm going to merge this, and then @ahoppen can rebase/resolve the conflict. He is working on making the codebase more robust, so thats definitely a good change. This was less invasive though. |
This adds a couple of changes to support building SwiftSyntax without an ObjC
runtime as well as swift-corelibs-foundation instead of the ObjC Foundation
implemetation. This is needed to support building SwiftSyntax on Linux.
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.
Resolves SR-NNNN.