2016-09-18 20:50:08 -07:00
[ CmdletBinding ( ) ]
param (
2018-06-12 17:12:33 -07:00
$badParam ,
2018-06-13 11:21:12 -07:00
[ Parameter ( Mandatory = $False ) ] [ switch ] $win64 = $false ,
2018-06-08 13:31:57 -07:00
[ Parameter ( Mandatory = $False ) ] [ string ] $withVSPath = " " ,
2021-02-04 10:15:44 -08:00
[ Parameter ( Mandatory = $False ) ] [ string ] $withWinSDK = " " ,
[ Parameter ( Mandatory = $False ) ] [ switch ] $disableMetrics = $false
2016-09-18 20:50:08 -07:00
)
2018-02-28 18:44:57 -08:00
Set-StrictMode -Version Latest
2018-06-12 17:12:33 -07:00
# Powershell2-compatible way of forcing named-parameters
if ( $badParam )
{
if ( $disableMetrics -and $badParam -eq " 1 " )
{
2021-02-04 10:15:44 -08:00
Write-Warning " 'disableMetrics 1' is deprecated, please change to 'disableMetrics' (without '1'). "
2018-06-12 17:12:33 -07:00
}
else
{
2021-02-04 10:15:44 -08:00
throw " Only named parameters are allowed. "
2018-06-12 17:12:33 -07:00
}
}
2021-02-04 10:15:44 -08:00
if ( $win64 )
2018-05-19 17:54:50 -07:00
{
2021-02-04 10:15:44 -08:00
Write-Warning " -win64 no longer has any effect; ignored. "
2018-05-19 17:54:50 -07:00
}
2021-02-04 10:15:44 -08:00
if ( -Not [ string ] :: IsNullOrWhiteSpace ( $withVSPath ) )
2018-05-19 17:54:50 -07:00
{
2021-02-04 10:15:44 -08:00
Write-Warning " -withVSPath no longer has any effect; ignored. "
}
2018-05-19 17:54:50 -07:00
2021-02-04 10:15:44 -08:00
if ( -Not [ string ] :: IsNullOrWhiteSpace ( $withWinSDK ) )
{
Write-Warning " -withWinSDK no longer has any effect; ignored. "
2018-05-19 17:54:50 -07:00
}
2018-02-22 19:56:08 -08:00
2021-02-04 10:15:44 -08:00
$scriptsDir = split-path -parent $script:MyInvocation . MyCommand . Definition
2018-05-19 19:38:45 -07:00
$vcpkgRootDir = $scriptsDir
2018-05-05 04:23:19 -07:00
while ( ! ( $vcpkgRootDir -eq " " ) -and ! ( Test-Path " $vcpkgRootDir \.vcpkg-root " ) )
2017-08-25 23:25:41 -07:00
{
2018-05-05 04:23:19 -07:00
Write-Verbose " Examining $vcpkgRootDir for .vcpkg-root "
$vcpkgRootDir = Split-path $vcpkgRootDir -Parent
2017-08-25 23:25:41 -07:00
}
2018-05-19 17:50:51 -07:00
2021-02-04 10:15:44 -08:00
Write-Verbose " Examining $vcpkgRootDir for .vcpkg-root - Found "
2018-05-05 04:23:19 -07:00
Update vcpkg-tool to 2022-03-25 (#23757)
* Update vcpkg-tool to 2022-03-24
* Hook up https://github.com/microsoft/vcpkg-tool/pull/345
* Hook up https://github.com/microsoft/vcpkg-tool/pull/442
* Update vcpkg-tool to 2022-03-25
* Analysis of failures.
* [Most recent nightly build failed](https://dev.azure.com/vcpkg/public/_build/results?buildId=69427)
* [Validation of this tool update failed](https://dev.azure.com/vcpkg/public/_build/results?buildId=69417)
## Common to both:
PASSING, REMOVE FROM FAIL LIST: chartdir:x64-windows (.\scripts\ci.baseline.txt)
PASSING, REMOVE FROM FAIL LIST: chartdir:x64-windows-static-md (.\scripts\ci.baseline.txt)
PASSING, REMOVE FROM FAIL LIST: chartdir:x86-windows (.\scripts\ci.baseline.txt)
Probably fixed by https://github.com/microsoft/vcpkg/pull/23701
PASSING, REMOVE FROM FAIL LIST: gmp:x64-uwp (.\scripts\ci.baseline.txt)
PASSING, REMOVE FROM FAIL LIST: gmp:x64-windows-static-md (.\scripts\ci.baseline.txt)
Probably fixed by https://github.com/microsoft/vcpkg/pull/23466 ?
REGRESSION: colmap:x64-windows-static-md failed with BUILD_FAILED. If expected, add colmap:x64-windows-static-md=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
I don't know exactly what changed. I observe that
* this thing depends on a *lot* of stuff
* on March 14 we didn't even attempt to build this
* the x64-windows ones are already in the baseline
so I skipped it.
REGRESSION: qtdeclarative:x64-windows. If expected, add qtdeclarative:x64-windows=fail to .\scripts\ci.baseline.txt.
REGRESSION: qtdeclarative:x64-windows failed with BUILD_FAILED. If expected, add qtdeclarative:x64-windows=fail to C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: qtdeclarative:x64-windows failed with BUILD_FAILED. If expected, add qtdeclarative:x64-windows=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: qtdeclarative:x64-windows failed with BUILD_FAILED. If expected, add qtdeclarative:x64-windows=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: qtdeclarative:x64-windows failed with BUILD_FAILED. If expected, add qtdeclarative:x64-windows=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: qtdeclarative:x64-windows failed with BUILD_FAILED. If expected, add qtdeclarative:x64-windows=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: qtdeclarative:x64-windows failed with BUILD_FAILED. If expected, add qtdeclarative:x64-windows=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: qtdeclarative:x64-windows failed with BUILD_FAILED. If expected, add qtdeclarative:x64-windows=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
This is a reporting change: The new world order also includes host build failures which is why it's duplicated.
See also https://github.com/microsoft/vcpkg/issues/23714
See also https://github.com/microsoft/vcpkg/issues/23490
I'm nervous about baslining this because it seems most of the qt world is built on top of this port
I filed https://github.com/microsoft/vcpkg/issues/23824 about this and @Neumann-A indicated this should be fixed by https://github.com/microsoft/vcpkg/pull/23755
REGRESSION: nettle:x64-uwp. If expected, add nettle:x64-uwp=fail to .\scripts\ci.baseline.txt.
REGRESSION: nettle:x64-windows-static-md. If expected, add nettle:x64-windows-static-md=fail to .\scripts\ci.baseline.txt.
REGRESSION: nettle:x64-uwp failed with BUILD_FAILED. If expected, add nettle:x64-uwp=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: nettle:x64-windows-static-md failed with POST_BUILD_CHECKS_FAILED. If expected, add nettle:x64-windows-static-md=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
Didn't analyze, probably fixed by https://github.com/microsoft/vcpkg/pull/23519 ?
REGRESSION: libgpg-error:x64-uwp. If expected, add libgpg-error:x64-uwp=fail to .\scripts\ci.baseline.txt.
REGRESSION: libgpg-error:x64-uwp failed with BUILD_FAILED. If expected, add libgpg-error:x64-uwp=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
This was broken by VS2022 update:
```
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.AppXPackage.Targets(892,25): error MSB4086: A numeric comparison was attempted on "$(TargetPlatformMinVersion)" that evaluates to "" instead of a number, in condition "'$(TargetPlatformMinVersion)' >= '10.0.17200.0'". [C:\Dev\vcpkg\buildtrees\libgpg-error\x64-uwp-rel\error-1.42-2324ddbc71.clean\SMP\libgpg-error_winrt.vcxproj]
```
REGRESSION: libmikmod:x64-osx. If expected, add libmikmod:x64-osx=fail to .\scripts\ci.baseline.txt.
REGRESSION: libmikmod:x64-osx failed with BUILD_FAILED. If expected, add libmikmod:x64-osx=fail to /Users/vagrant/Data/work/2/s/scripts/azure-pipelines/../ci.baseline.txt.
Broken between [2022-03-16](https://dev.azure.com/vcpkg/public/_build/results?buildId=68947) and [2022-03-18](https://dev.azure.com/vcpkg/public/_build/results?buildId=69051). Unfortunately I don't see obvious reasons why. Nothing else depends on this and nobody has noticed in 2 weeks, so I'm baslining it for now. (Will investigate shortly...)
## Only broken in tool update:
REGRESSION: mesa:x64-windows failed with BUILD_FAILED. If expected, add mesa:x64-windows=fail to C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt.
```
-- Downloading https://gitlab.freedesktop.org/mesa/mesa/-/archive/mesa-21.2.5/mesa-mesa-21.2.5.tar.gz -> mesa-mesa-mesa-21.2.5-1.tar.gz...
-- Extracting source /Users/vagrant/Data/downloads/mesa-mesa-mesa-21.2.5-1.tar.gz
-- Applying patch swravx512-post-static-link.patch
-- Applying patch swr-msvc-2.patch
-- Applying patch swr-llvm13.patch
-- Applying patch radv-msvc-llvm13-2.patch
-- Applying patch d3d10sw.patch
-- Using source at /Users/vagrant/Data/buildtrees/mesa/src/esa-21.2.5-2df234d2b1.clean
Traceback (most recent call last):
File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'mako'
CMake Error at ports/mesa/portfile.cmake:85 (message):
Python package 'mako' needs to be installed for port 'mesa'.
Complete list of required python packages: setuptools;mako
Call Stack (most recent call first):
ports/mesa/portfile.cmake:91 (vcpkg_get_python_package)
scripts/ports.cmake:145 (include)
```
Looks like this is being tracked by https://github.com/microsoft/vcpkg/pull/23089 ; perhaps that we don't have as aggressive a recycling strategy for macos boxes as we do for the others has let different machines give different results?
## Only broken without tool update:
REGRESSION: chromium-base:x64-osx. If expected, add chromium-base:x64-osx=fail to .\scripts\ci.baseline.txt.
This one has been constantly flaky; I baselined it.
REGRESSION: libxml2:x64-osx. If expected, add libxml2:x64-osx=fail to .\scripts\ci.baseline.txt.
This port uses vcpkg_from_git and the upstream server was down during the build.
* Restore chartdir to the baseline, I thought https://github.com/microsoft/vcpkg/pull/23732 had been merged.
2022-03-28 13:17:35 -07:00
$versionDate = '2022-03-25'
2022-01-21 14:10:58 -05:00
if ( $env:PROCESSOR_ARCHITECTURE -eq 'ARM64' -or $env:PROCESSOR_IDENTIFIER -match " ARMv[8,9] \(64-bit\) " ) {
& " $scriptsDir /tls12-download.exe " github . com " /microsoft/vcpkg-tool/releases/download/ $versionDate /vcpkg-arm64.exe " " $vcpkgRootDir \vcpkg.exe "
2021-10-29 22:39:14 -07:00
} else {
& " $scriptsDir /tls12-download.exe " github . com " /microsoft/vcpkg-tool/releases/download/ $versionDate /vcpkg.exe " " $vcpkgRootDir \vcpkg.exe "
}
2021-02-04 10:15:44 -08:00
Write-Host " "
2016-09-18 20:50:08 -07:00
2021-02-04 10:15:44 -08:00
if ( $LASTEXITCODE -ne 0 )
2017-08-25 23:25:41 -07:00
{
2021-02-04 10:15:44 -08:00
Write-Error " Downloading vcpkg.exe failed. Please check your internet connection, or consider downloading a recent vcpkg.exe from https://github.com/microsoft/vcpkg-tool with a browser. "
2020-07-01 10:53:10 -07:00
throw
2016-09-18 20:50:08 -07:00
}
2020-07-01 10:53:10 -07:00
2021-01-13 14:06:06 -08:00
if ( $disableMetrics )
{
Set-Content -Value " " -Path " $vcpkgRootDir \vcpkg.disable-metrics " -Force
}
elseif ( -Not ( Test-Path " $vcpkgRootDir \vcpkg.disable-metrics " ) )
2020-02-13 18:12:12 -08:00
{
2021-01-13 14:06:06 -08:00
# Note that we intentionally leave any existing vcpkg.disable-metrics; once a user has
# opted out they should stay opted out.
2020-02-13 18:12:12 -08:00
Write-Host @"
2019-11-14 13:12:36 -08:00
Telemetry
- - - - - - - - -
2020-05-29 14:09:03 -07:00
vcpkg collects usage data in order to help us improve your experience .
The data collected by Microsoft is anonymous .
You can opt-out of telemetry by re-running the bootstrap-vcpkg script with -disableMetrics ,
passing - -disable -metrics to vcpkg on the command line ,
or by setting the VCPKG_DISABLE_METRICS environment variable .
2019-11-14 13:12:36 -08:00
2020-05-29 14:09:03 -07:00
Read more about vcpkg telemetry at docs / about / privacy . md
2019-11-14 13:12:36 -08:00
" @
2020-02-13 18:12:12 -08:00
}