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

Roadblocks roadblocks

This commit is contained in:
Pietro Gagliardi 2019-04-07 01:43:31 -04:00
parent 5ded8398ba
commit f7c1515ae1
1 changed files with 2 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -6,13 +6,9 @@ parameters:
steps: steps:
- powershell: | - powershell: |
Set-PSDebug -Trace 2 Set-PSDebug -Trace 2
$MyInvocation | Write-Host
$MyInformation.MyCommand | Write-Host
$MyInformation.MyCommand.Definition | Write-Host
Write-Host "$MyInvocation.MyCommand.Definition"
Write-Host "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
ls "$env:ChocolateyInstall" | Write-Host ls "$env:ChocolateyInstall" | Write-Host
ls "$env:ChocolateyInstall\lib\mingw" | Write-Host 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
$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)