This commit is contained in:
Pietro Gagliardi 2019-04-07 01:50:53 -04:00
parent f7c1515ae1
commit 23a0a041f0
1 changed files with 3 additions and 4 deletions

View File

@ -6,14 +6,13 @@ parameters:
steps: steps:
- powershell: | - powershell: |
Set-PSDebug -Trace 2 Set-PSDebug -Trace 2
ls "$env:ChocolateyInstall" | Write-Host ls "$env:ChocolateyInstall\lib\mingw\tools\install"
ls "$env:ChocolateyInstall\lib\mingw"
ls "$env:ChocolateyInstall\lib\mingw\tools" | Write-Host
where.exe mingw32-make.exe | Write-Host where.exe mingw32-make.exe | Write-Host
where.exe gcc.exe | Write-Host
$chocopath = where.exe choco.exe | Get-Item $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) # 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" $chocopath = Join-Path -Path $chocopath.Directory -ChildPath "install" | Join-Path -ChildPath "${{ parameters.which }}" | Join-Path -ChildPath "bin"
ls $chocopath | Write-Host ls $chocopath
Write-Error "##vso[task.prependpath]$chocopath" Write-Error "##vso[task.prependpath]$chocopath"
exit 1 exit 1
displayName: 'Set Up MinGW-w64' displayName: 'Set Up MinGW-w64'