-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[all OSs] The VCPKG_ROOT variable will be removed from runner images #6376
Comments
Removal date shifted one week. |
By removing builin-baseline constraint, we force vcpkg to use latest versions of ports. As a side effect, this bumps OpenSSL to 3.0.7. While on it, update vcpkg commit in GHA. We also have to apply a workaround for GHA to make it use our vcpkg checkout instead of c:\vcpkg, see actions/runner-images#6376 lukka/run-vcpkg#170 Signed-off-by: Lev Stipakov <[email protected]>
By removing builin-baseline constraint, we force vcpkg to use latest versions of ports. As a side effect, this bumps OpenSSL to 3.0.7. While on it, update vcpkg commit in GHA. We also have to apply a workaround for GHA to make it use our vcpkg checkout instead of c:\vcpkg, see actions/runner-images#6376 lukka/run-vcpkg#170 Signed-off-by: Lev Stipakov <[email protected]>
By removing builin-baseline constraint, we force vcpkg to use latest versions of ports. As a side effect, this bumps OpenSSL to 3.0.7. While on it, update vcpkg commit in GHA. We also have to apply a workaround for GHA to make it use our vcpkg checkout instead of c:\vcpkg, see actions/runner-images#6376 lukka/run-vcpkg#170 Signed-off-by: Lev Stipakov <[email protected]>
By removing builin-baseline constraint, we force vcpkg to use latest versions of ports. As a side effect, this bumps OpenSSL to 3.0.7. While on it, update vcpkg commit in GHA. We also have to apply a workaround for GHA to make it use our vcpkg checkout instead of c:\vcpkg, see actions/runner-images#6376 lukka/run-vcpkg#170 Signed-off-by: Lev Stipakov <[email protected]>
Now that VCPKG_ROOT is not defined anymore, For people that use the installation that comes with the image you can set VCPKG_ROOT to VCPKG_INSTALLATION_ROOT with this step.
|
By removing builin-baseline constraint, we force vcpkg to use latest versions of ports. As a side effect, this bumps OpenSSL to 3.0.7. While on it, update vcpkg commit in GHA. We also have to apply a workaround for GHA to make it use our vcpkg checkout instead of c:\vcpkg, see actions/runner-images#6376 lukka/run-vcpkg#170 Signed-off-by: Lev Stipakov <[email protected]> Acked-by: Gert Doering <[email protected]> Message-Id: <[email protected]> URL: https://www.mail-archive.com/[email protected]/msg25474.html Signed-off-by: Gert Doering <[email protected]>
Deployed |
Make the path to the vcpkg executable explicit to avoid relying on VCPKG_ROOT which had been changed (and then reverted) on github actions runners, see actions/runner-images#6376
See here: actions/runner-images#6376 (comment). This alone might not be enough yet.
This documentation: promises an environment variable
The variable seems to be not there. I tried a few variations:
|
Breaking changes
The VCPKG_ROOT variable will be removed from runner images.
Target date
October, 31. The propagation will take 2-3 days.
The motivation for the changes
In accordance with the reaction of the VCPKG developers and community to the recent changes regarding the setting of the VCPKG_ROOT variable, it was decided to abandon such breaking changes so that users can independently control the contents of this environment variable.
The history of changes and reasons for cancellation can be found here: #6146, #6192, #6195, #6196.
Possible impact
Users who have already started using the VCPKG_ROOT variable in accordance with the latest changes may encounter some difficulties.
Platforms affected
Runner images affected
Mitigation ways
Users who have already started using the VCPKG_ROOT variable in accordance with the latest changes should revert to using the VCPKG_INSTALLATION_ROOT variable to avoid errors.
The text was updated successfully, but these errors were encountered: