Don't compile symbols for Linux that are not yet available #22
Conversation
|
@davdroman Bummer! But sounds like a good fix. I wonder if we should update Linux CI to work against Swift 5.5 (and maybe other versions, as well). |
|
@stephencelis I'm happy to assist with that in this PR or a separate one (up to you). Docker images for Swift 5.5 are out now so it shouldn't be too complicated to do. |
|
@davdroman If you'd like to take a stab please do! It'd be cool to see the failure on that PR branch for what's being fixed on this one. We already have a Windows failure on main due to the order of merging PRs yesterday, ha, so the more robust our CI the better. We'll try to get around to fixing the Windows test failure tomorrow so that this PR can turn green. |
|
@stephencelis here we go! #23 |
stephencelis
left a comment
stephencelis
left a comment
There was a problem hiding this comment.
Great, gonna merge this and see how the other PRs fare!
* CI: Enable Swift 5.5 Linux builds * Update README.md * Don't compile symbols for Linux that are not yet available (#22) Co-authored-by: Stephen Celis <stephen@stephencelis.com>
2 participants
Basically the same as #20 but for Linux this time. This PR fixes Swift 5.5 compilation on Linux.
Backstory: Swift 5.5 images don't come bundled with a version of Foundation containing
AttributedStringyet. Whilst the changes are in the upstream branch, a release hasn't been made yet — I believe because macOS 12 is not out yet and Apple wants parity with "Apple Foundation".