Chris McGee
Chris McGee
See https://github.com/swiftlang/github-workflows/blob/main/.github/workflows/swift_package_test.yml#L12C9-L12C50
The TOOLCHAINS environment variable is related to working with Xcode. At the moment the swiftly integration is mostly just at the macOS level.
> Currently I'm just removing swiftly from my PATH when I want Xcode swift Another approach that I use from time-to-time is to directly run `/usr/bin/swift` when I want the...
Thanks for bringing this up. It appears that the OpenAPI generator doesn't support Windows at all. Neither does Swift NIO at the moment. These will need to be figured out...
I don't think that it can hurt to raise an issue on NIO. They might duplicate it if there's an existing one tracking Windows support.
@MahdiBM we don't really have a contributors guide at the moment. But, we do have a subcommand of swiftly devoted to configuring and installing itself that should work in dev...
@patricktcoakley swiftly relying entirely on the swift.org API for this. If there's a discrepancy in the API then I think that this issue belongs on the swift-org-website repository.
@patricktcoakley when you ran the above list-available command, I'm assuming that you were on macOS at the time? This JSON does seem to indicate that there is a macOS toolchain...
Would PR #317 be sufficient to support switching between the Xcode selected toolchain and one of the swiftly installed ones?
@MahdiBM the new install mechanism through the `swiftly init` subcommand uses the login shell instead of the current shell. Does this address the original problem?