-
Notifications
You must be signed in to change notification settings - Fork 3k
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
The latest vcpkg is broken, please don't take it #1332
Comments
Hello @snnn , Thank you for reaching us. |
Yes! |
It seems that CMake 18 is the culprint and it already hit the pipelines like here: So please make a hotfix when VCPKG has solved its bug. |
This has tanked our Windows CI workflows since Monday. |
Just to merge discussions in #1340 and this issue: cc: @strega-nil |
@maxim-lobanov , drop an update when the new Windows GitHub images are regenerated w/ the upated vcpkg. 👍 Going on day 8 now with Windows CI broken, so can't wait for the fix 🙌 |
Hello, I am closing this issue but if you have any other suggestions how we can improve installation process from our side, we are ready to continue discussion |
Describe the bug
see: microsoft/vcpkg#12565
I know your team usually generates a new set of images every week. But, the build script always take vcpkg from master, it is kind of dangerous. Please consider to use tags. The issue 12565 is an example, if you rebuild the image now, you'll have the bug, and would break all the vcpkg Windows users.
Area for Triage:
C/C++
Question, Bug, or Feature?:
Bug
Virtual environments affected
Expected behavior
Rebuild the image
Try to use vcpkg to install protobuf/libffi or some other open source libraries
The should work fine
Actual behavior
It fails, even through it's not your fault. Here just kindly remind you there is a problem. Please feel free to close this issue without taking extra actions.
The text was updated successfully, but these errors were encountered: