ci: Set MSVC toolset version explicitly#28934
Conversation
The GHA VS installation includes its own vcpkg package manager, which is available since VS 17.6. This change avoids any ambiguity about which copy of vcpkg we run.
This change avoids toolset incompatibilities that cause linker errors.
This reverts commit 91d5bd8.
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code CoverageFor detailed information about the code coverage, see the test coverage report. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. |
|
Does the CI job still cache the vcpkg dependencies? Will this PR still work if there a minor version update on the build image? |
It does.
I've added the toolset version to the cache key: bitcoin/.github/workflows/ci.yml Line 250 in 70100f8 so the cache will be invalidated if it is changed. |
Wrong hash? :) |
|
Seems fine to do this, if this makes CI faster and there are no major downsides |
This PR is an alternative to #28905 and reverts it.
To avoid toolset version incompatibilities, which result in errors like this:
it is enough to set it explicitly in the vcpkg triplet file (see the second commit). The
VCToolsVersionenvironment variable is set by theilammy/msvc-dev-cmdaction.Please note that the #28905 is not optimal: