libui/azure-pipelines/windows-setup-mingw.yml

20 lines
998 B
YAML

# 7 april 2019
parameters:
which: 'must-be-specified'
steps:
- powershell: |
Set-PSDebug -Trace 2
ls "$env:ChocolateyInstall" | Write-Host
ls "$env:ChocolateyInstall\lib\mingw"
ls "$env:ChocolateyInstall\lib\mingw\tools" | Write-Host
where.exe mingw32-make.exe | Write-Host
$chocopath = where.exe choco.exe | Get-Item
# apparently they didn't think to add this functionality from the start (multiple joins was only added in PowerShell 6 and Azure Pipelines is using 5.x), and the direct-CLR approach actually behaves differently (and I would need to check which version of .net Azure Pipelines is using anyway, since our use case isn't one of those cases where it behaves differently)
$chocopath = Join-Path -Path $chocopath.Directory -ChildPath "install" | Join-Path -ChildPath "${{ parameters.which }}" | Join-Path -ChildPath "bin"
ls $chocopath | Write-Host
Write-Error "##vso[task.prependpath]$chocopath"
exit 1
displayName: 'Set Up MinGW-w64'