You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure why did we strip this path during binary release? The benefits of including toolchain's library rpath is that you no longer need to worry about SwiftSyntax dylib as long as you have Xcode installed. This will make installation & distribution of mockingbird CLI much simpler.
The text was updated successfully, but these errors were encountered:
We distribute the _InternalSwiftSyntaxParser library with the binary because SwiftSyntax has strict version requirements. For example, SwiftSyntax for Swift 5.4 cannot be load the parser from the Swift 5.5 toolchain or it’ll exit out. More specifically, the Swift syntax node layout isn’t guaranteed to be stable.
@andrewchang-bird Understood. How about considering the idea of distributing Swift version-specific binaries in addition to the existing release model? For example: mockingbird-swift-5.5.zip
New Feature Request Checklist
Overview
The downloaded mockingbird CLI binary doesn't seem to include the toolchain's std library path. Run
otool -l mockingbird
If I build the CLI from source using the following command, Swift will by default include toolchain's library path as rpath
And
otool -l mockingbird
outputsNot sure why did we strip this path during binary release? The benefits of including toolchain's library rpath is that you no longer need to worry about SwiftSyntax dylib as long as you have Xcode installed. This will make installation & distribution of mockingbird CLI much simpler.
The text was updated successfully, but these errors were encountered: