-
Notifications
You must be signed in to change notification settings - Fork 48
Swiftly is incompatible with Swift shipped in Xcode #301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
There should be some kind of way to disable My only workaround is to comment the swiftly # Set the toolchain to the latest installed:
# export TOOLCHAINS=$(plutil -extract CFBundleIdentifier raw /Library/Developer/Toolchains/swift-latest.xctoolchain/Info.plist) If you have an open Terminal window, you'll probably also need to unset TOOLCHAINS: export TOOLCHAINS="" |
swiftly enable / swiftly disable is probably a good feature overall anyway! Kind of like brew link / brew unlink, it gives the user maximum freedom with their PATH, linker search paths, etc. Probably any attempt of using swiftly when disabled should at least prompt the user about it, if not outright fail on "swiftly use" |
I don't know if it's relevant, but it seems like toolchain installed via Swiftly breaks code completion in Xcode (in VSCode it works well though) |
I assume #315 fixes this issue? |
Swiftly needs functionality to let the user switch between Xcode and the Open-Source Swift toolchains. If a user installs swiftly today on macOS, any use of
swift
from the command line will only ever use the currently selected Swiftly-selected toolchain.The text was updated successfully, but these errors were encountered: