Update vcpkg-tool to 2022-01-19

[BillyONeal]

No description provided.

[autoantwort]

The ci command segfaults

[autoantwort]

Would be fixed by microsoft/vcpkg-tool#327

[autoantwort]

Ok not completely, it then fails at

Starting package 4/1734: absent:x64-osx
Building package absent:x64-osx...
-- Using cached rvarago-absent-0.3.1.tar.gz.
-- Extracting source /Users/leanderSchulten/git_projekte/Lichtsteuerung/vcpkg/downloads/rvarago-absent-0.3.1.tar.gz
-- Using source at /Users/leanderSchulten/git_projekte/Lichtsteuerung/vcpkg/buildtrees/absent/src/0.3.1-40487c5ce5.clean
-- Configuring x64-osx-dbg
-- Configuring x64-osx-rel
-- Building x64-osx-dbg
-- Building x64-osx-rel
-- Installing: /Users/leanderSchulten/git_projekte/Lichtsteuerung/vcpkg/packages/absent_x64-osx/share/absent/README.md
-- Installing: /Users/leanderSchulten/git_projekte/Lichtsteuerung/vcpkg/packages/absent_x64-osx/share/absent/copyright
-- Performing post-build validation
-- Performing post-build validation done
Error: vcpkg has crashed; no additional details are available.
The source line is /Users/leanderSchulten/git_projekte/vcpkg-tool/src/vcpkg/build.cpp(958)

[BillyONeal]

Ok not completely, it then fails at

Right, that change sees when nulls happen and skips over them, but it doesn't fix that nulls got in there in the first place which is the actual bug. It regressed in microsoft/vcpkg-tool#298 and I'm investigating.

[BillyONeal]

microsoft/vcpkg-tool#329 is my current WIP after spending all day trying to diagnose the issue

[autoantwort]

Maybe change ports.cmake to trigger a full rebuild

[BillyONeal]

Maybe change ports.cmake to trigger a full rebuild

That would trigger a rebuild for customers too which is undesirable.

[autoantwort]

I mean you only change it to trigger a full rebuild to test if everything still works. If everything still works you revert the change again.

Edit: Otherwise there is only microsoft/vcpkg-tool#310 that could break some ports. No new post build check was introduced. So yeah you maybe don't need to rebuild everything to test this new version.

[BillyONeal]

I mean you only change it to trigger a full rebuild to test if everything still works. If everything still works you revert the change again.

Oh, I see. I suppose getting a full run is a good idea. For that I can just trigger a CI run: https://dev.azure.com/vcpkg/public/_build/results?buildId=66773&view=results