interesting
/
libui
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

That didn't quite work

This commit is contained in:
Pietro Gagliardi 2019-04-07 00:43:41 -04:00
parent d3c553c424
commit 651d502624
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
azure-pipelines/windows-setup-mingw.yml
View File

@ -8,6 +8,7 @@ steps:
$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"
echo "abcdef##vso[task.prependpath]$chocopath" dir $chocopath | Write-Error
Write-Error "##vso[task.prependpath]$chocopath"
exit 1 exit 1
displayName: 'Set Up MinGW-w64' displayName: 'Set Up MinGW-w64'