Windows Support

[AlistairB]

#3

To Do

• Remove ghc profiling files
• Remove ghc docs
• Remove stack docs
• stack setup is failing with missing ca certs, possibly due to msys2 issue?
• Is gpg usable? Doubtful as no other official images appear to do it.
• Add all windows variants
• Add all ghc versions
• Consider general reorder of installation for better layer caching between ghc versions.
• Decide when to release.
• Should there be ENV or ARG for any of the versions?
• Look at chocolatey for ghc / cabal / stack install in case there is something interesting.
• Read through ghcup more to see if there might be something we are missing.

Status

I believe the built image actually works. Now it is a matter of testing it and figuring out how CI works. The hard part of this is trying to rig up stack to use the inbuilt msys2 as per the below.

Blockers

Can't use existing msys2 with stack

EDIT: Ok this is not really a blocker, as ghcup notes users should be able to use the inbuilt msys2 via skip-msys, extra-path, extra-include-dirs, extra-lib-dirs stack flags. I believe this is necessary because when the GUI installer is not used the bundled stack msys2 is not installed.

There doesn't seem to be a way to nicely either use an existing msys2 install with stack, or install the bundled msys2 that the stack GUI installer installs.

Relevant issues:

• Redundant output when running stack with previously installed msys2 commercialhaskell/stack#1495
• Consider add stack config set skip-msys --global commercialhaskell/stack#5573
• https://stackoverflow.com/questions/70483264/why-doesnt-stack-installed-by-ghcup-find-msys-installed-by-ghcup-on-windows