-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add support for NixOS #7528
Comments
Looks like we are not detecting NixOS as a Linux OS here: swift-package-manager/Sources/PackageLoading/Platform.swift Lines 43 to 53 in 32442c6
What does |
Here are the results:
|
Synced to Apple’s issue tracker as rdar://127491941 |
Interesting, that definitely is what we are expecting Which version of SourceKit-LSP are you using? Ie. which Swift toolchain do you have installed? If it’s some Swift 5 version, could you try if the issue still reproduces with a Swift 6 development snapshot from https://www.swift.org/download/#swift-60-development? I’ve made a lot of improvements to SourceKit-LSP during the Swift 6 development cycle and I vaguely remember seeing that log message before but can’t remember when or if I fixed it. |
I can definitely give that a try, might take me a little bit to figure out how to get everything all set up though |
Ah, I remember now: I was seeing a similar issue at some point because for some reasons (I can’t remember the details) The problem here is that we only detect swift-package-manager/Sources/PackageLoading/Platform.swift Lines 57 to 77 in 32442c6
With that information, it’s not necessary for you to test the Swift 6 snapshot since it also won’t have support for NixOS. I’ll move the issue over to SwiftPM because that’s where the platform detection logic lives. |
When trying to invoke
sourcekit-lsp
on Nix, I get an error:2024-05-03 14:47:53.510 sourcekit-lsp[25781:4ffff6c0] Could not determine host OS. Falling back to using '.so' as dynamic library extension
Is adding NixOS support a possibility / planned for the future?
The text was updated successfully, but these errors were encountered: