issue when trying to run swift script.

[Nytem]

so I followed the getting started page for the windows installation (https://swift.org/getting-started/) but every time I try to run a swift script I get this popup.

any ideas what could be going on?

[stevapple]

This is a known restriction of the legacy Swift driver. With the release of Swift 5.7, Swift has officially adopted the new driver on Windows, so this error should not appear any more with Swift 5.7+.

Give the new Swift 5.7 a shot and see if anything is different?

[Nytem]

I did download swift 5.7 I believe, it was the latest one in the downloads section.

[Nytem]

wait nope it's showing as 5.6.3??? mb

[Nytem]

ok it ran but now I got this

[adam-fowler]

@compnerd any ideas, what is happening here

[compnerd]

That indicates that the environment is not correct (i.e. SDKROOT is unset). Most likely the shell/terminal emulator was not restarted after the update.

[Nytem]

let me try restarting everything then quickly

[Nytem]

@compnerd restarted everything and still getting the same issue

[compnerd]

Run set SDKROOT and ensure that the path exists and is correct. I assume that you did do an uninstall + install for the upgrade?

[Nytem]

yeah I uninstalled swift 5.6.3 and then installed 5.7

[Nytem]

where do I enter that set SDKROOT, sorry I'm a little bit incompetent here lol, just my class for school requires swift and I own no apple devices so I'm just trying to get this working lol

[compnerd]

You should be able to run that from a cmd prompt.

[Nytem]

yeah ok a path does exist

SDKROOT=C:\Library\Developer\Platforms\Windows.platform\Developer\SDKs\Windows.sdk

[compnerd]

I wonder if the problem is that the plugin is erasing the SDKROOT environment variable? @stevapple or @adam-fowler would know that better.

[Nytem]

wonder if the standard library is even there perhaps? would you know what the name of the folder I should be looking for is?

[stevapple]

@Nytem Did you see the error when manually running swift <script.swift> from a developer command prompt?

The plugin doesn't modify the environment without configuration (except for testing). I see this as something wrong with SDK/toolchain layout.

[Nytem]

@stevapple I just right clicked, and then under swift I clicked run swift script

[compnerd]

You will find the standard library swift module %SDKROOT%\usr\lib\swift\windows\Swift.swiftmodule, the import library at %SDKROOT%\usr\lib\swift\windows\x86_64, and the runtime in C:\Program Files\swift\runtime-development\usr\bin.

[Nytem]

these all look correct?

[stevapple]

@Nytem I just want to make sure that the toolchain works without the plugin. Run Swift Script is a very simple feature and it's unlikely to impact the driver.

Can you open x64 Native Tools Command Prompt from start menu, cd path\to\workspace, and manually run swift script.swift? A screenshot of the command outputs will help a lot.

[Nytem]

@stevapple like this?

[Nytem]

sorry for the blackouts, folders named somewhat personal info lol

[stevapple]

@stevapple like this?

Almost right -- except that CMD doesn't specialize ', so you should use " to wrap the argument instead. Could you try again?

[Nytem]

oh oops, will do

[Nytem]

same issue

[compnerd]

What if you do an explicit swift -sdk %SDKROOT% "..."?

[Nytem]

exact same error

[compnerd]

Hmm, running with -v might be useful to see what the driver is doing. In general, the interpreter is not supported on Windows, compiling and executing is.

[Nytem]

[Nytem]

so when following the getting started page, it said I needed python, if I type in python --version it doesn't detect anything... could that be the issue?

[Nytem]

nope nvm, I just installed it all again, restarted everything, and still same standard library error

[stevapple]

@compnerd Looks like the 5.7 driver is still trying to use interpreter. Did you recognize any commit possibly forgotten for cherry-picking to 5.7 branch?

[stevapple]

@Nytem I reproduced the problem locally and this is a driver bug instead of the plugin’s. Could you please open a new issue in apple/swift-driver, so we can move on there? This issue can be closed then.

[Nytem]

alright, will do. thanks for the help guys!

[Nytem]

apple/swift-driver#1182