Appveyor builds fail looking for Curl

[epage]

Example

If ($Env:TARGET -eq 'x86_64-pc-windows-gnu') {
  $Env:PATH += ';C:\msys64\mingw64\bin'
} ElseIf ($Env:TARGET -eq 'i686-pc-windows-gnu') {
  $Env:PATH += ';C:\msys64\mingw32\bin'
}
curl -sSf -o rustup-init.exe https://win.rustup.rs/
'curl' is not recognized as an internal or external command,
operable program or batch file.
Command exited with code 1

output for cobalt.rs

[epage]

I suspect it is related to the latest platform update

I found an appveyor support issue about curl not being found. It seems git previously put curl in the default path. That got me wondering if the paths used in trust were correct

The above issue mentions using git's mingw

C:\Program Files\Git\mingw64\bin

Appveyor's documentation for the build environment lists these paths

C:\MinGW\bin
C:\mingw-w64\i686-6.3.0-posix-dwarf-rt_v5-rev1
C:\mingw-w64\x86_64-6.3.0-posix-seh-rt_v5-rev1
# etc

I've not had a chance to try changing the path to see if they fix my builds.

[epage]

I just got a successful build with the workaround specified in appveyor/ci#1426

I added the line

$Env:PATH += ';C:\msys64\usr\bin'

Unconditionally to the path

[epage]

My PR to fix cobalt.rs: cobalt-org/cobalt.rs#205

[epage]

Someone brought up the idea of using Invoke-WebRequest

[japaric]

Someone brought up the idea of using Invoke-WebRequest

I have used that before and it was unreliable. Sometimes I got download / authentication failures when downloading rustup. I have had zero issues with curl.