Thanks @compnerd, Firstly all the work you have put in is awesome, thank you for that.
I'm not sure I understand what you are suggesting here. Are you suggesting that Swift/Win32 be part of the toolchain installation? Or that the binaries that it generates be in the same directory?
There are only 2 ways to get swift for windows,
- Download the source and compile it yourself
- Get a pre-compiled binary
Let's look at Option #1 first
There are a lot of dependencies that are required but they are not clear or if the only instructions required as as per the README.md file, then here's the issues
i. Systems may or may not have the cmake and ninja
ii. ninja may not be configured in the path variable
iii. The step [1/2] Linking Swift shared library bin\SwiftWin32.dll fails due to cannot find PARAFORMAT in scope, these are all in the UI/TextField.swift
So one might choose the other option, how about downloading the precompiled binary
i. The binary is the executable file called
ii. when run it installs and finishes
iii. Still swift, swiftc, repl_swift do not work
iv. Setup the swift flags, ensure that the components from Visual Studio Community 2019 are downloaded
v. change to the Examples, Calculator directory and run
swiftc -o swiftCalc Calculator.swift %SWIFTFLAGS%
it immediately complains that there is no such module,
import SwiftWin32. Wasn't that the idea of using the binary installer?
Plus Swift displays the ansi characters, swiftc breaks and does not render them correctly.
It makes it very difficult to even get started. It may be working for many - but it definitely does not work for the other half of the many devs trying this out.
Also the instructions have the slashes for Unix or Mac, where as it needs to be the other ones for Windows. So anyone following the instructions will always end up with frustration because of that.
Hence the suggestion to have a better installer or better instructions with a step-by-step guide on a fresh windows install that is not a developers set environment.