Enable a more portable binary on macOS - Approach 2

[liamnichols]

Background

• Using StaticInternalSwiftSyntaxParser? #473

To make the periphery binary more portable on macOS, we want to have the lib_internalSwiftSyntaxParser library statically linked into the binary instead of having to link to a dylib version somewhere on the system.

Approach 2

This is a second take on the approach used in #476, the main problem I'm trying to work around in these solutions is that I can't use binary targets in this Package.swift since it breaks swift package describe (SR-15243 and SR-15065).

In this approach, I work around that by using a fork of the apple/swift-syntax repo where I have made some minor modifications to the Package.swift file so that the StaticInternalSwiftSyntaxParser dependency is properly declared on the SwiftSyntax/SwiftSyntaxParser targets directly.

While forking the official dependency is somewhat of an inconvenience, it feels like the 'cleanest' approach since it avoids having to do other workarounds like the one used in the first approach, or like those that have to exist in SwiftLint/Sourcery.

Since the fork is only used to reconfigure the Package.swift, it doesn't feel like that big of a problem (we're just using it to re-tag the releases after patching), but ideally I'd like to transfer the fork/tags into the peripheryapp org as well.

Here are the diffs between the new tags in swift-syntax repo:

swiftlang/swift-syntax@0.50600.1...liamnichols:0.50600.1-static
swiftlang/swift-syntax@0.50500.0...liamnichols:0.50500.0-static

[ileitch]

Hey @liamnichols, thanks for digging into all of this. I've forked swift-syntax to the peripheryapp org, and given you write access. Feel free to copy over your changes, and then we can get this merged 👍

[liamnichols]

Thanks @ileitch! I've pushed the changes up as well as rebasing from master after merging #479 just to be 100% sure that everything is ✅ before merging this 🙇