the release number for swift-argument-parser has doubled since this summer, so it probably just needs a version bump. (feels like i just released it yesterday…)
at the time the plugin was written, package plugins were still very experimental so it depended on master of SwiftPM instead of a tagged release. in the 6 or so months since, that’s probably no longer the case.
in the meantime, can you file an issue on github with your platform and a small test project?
since it wouldn’t be swift if you weren’t holding it wrong, i have learned that swift binaries are just like any other type of binary and they search for libraries in the same directory that the toolchain lived in at the time when the binary was originally compiled.
in this thread i managed to compile with a dynamic standard library on a separate machine from the deployment target, by recreating the directory structure of the target machine.
it’s annoying, but at least we have a solution/workaround for it, which is more than can be said for a lot of other problems in this space
just reiterating. it's amazing that @futurejones does what he does
seriously, it could really make a whole world of difference.
obligatory retweet:
https://twitter.com/maxdesiatov/status/1451181896784744455?s=20&t=bV34Fm0jGR5ZaFaUPd6i6A
If you mean statically linking the Swift stdlib, Dispatch and Foundation*. Yes, it is supposed to work. It was however broken on 5.6 and main up until a few days ago. Announcement post on the forums
Open PRs to fix the issues on main (@Alejandro):
Just adding here for visibility - we have a new Swift Server Community org on GH that solves most of the issues asked here