vcpkg install quits immediately after printing Computing installation plan...
#18718
Comments
|
@wangqr could you try running |
|
|
Here's the output if I run the last 2 commands directly: Uninstalling CMake can resolve this issue. |
|
An issue with CMake 3.21.0-rc1, cf. #18636. |
|
Same issues with libusb and libusb-win32 :- `Microsoft Windows [Version 10.0.17134.1304] C:\Windows\system32>vcpkg install libusb --debug C:\Windows\system32>cmake --version CMake suite maintained and supported by Kitware (kitware.com/cmake). C:\Windows\system32> C:\Windows\system32>` |
And still the same version of cmake, which is only a release candidate.
|
|
Raised an issue at https://gitlab.kitware.com/cmake/cmake/-/issues/22367 if Kitware may take notice we will have CMAKE Windows on ARM64 binaries. 🤞 |
|
The original post here is for |
@wangqr , @sidd-kishan .Duplicate of #18636 |
|
Same issue here. I was trying the ARM64EC toolchain and I need vcpkg to work. It's tedious that I need to reinstall an older version of cmake every time I need to use vcpkg. I created an issue on Kitware's CMake repo: https://gitlab.kitware.com/cmake/cmake/-/issues/22371 |
|
I have also seen this issue and traced it to a regression in CMake 3.21.0-rc1. You get what appears to be the same output from CMake 3.20.5 but in reality some of the lines are delimited with '\r\n' and others '\n'. This causes an issue when the returned lines are split on each '\n' and then the searching function fails to find the inserted UUIDs delimiting the output for parsing. I will create a pull request with a fix and let the powers that be decide whether to try and ask Kitware to fix their regression or make VcPkg tolerant of line endings. |
Git bisect shows Kitware/CMake@0a0a0f8 introduced this the behavior, changing line breaks within a message from '\n' (old) to '\r\n' (new), and the auto-appended '\n' is not changed. |
|
I have created a pull request for the VcPkg tool here: |
|
Met the same issue when update CMake to 3.21.0 |
|
This should be fixed by #18983 ; can you try updating your git repository and re-bootstrap? |
|
Do you plan to publish a new release with this fix soon? |
Cache is improved, so vcpkg itself is not built every time. Upgrade of vcpkg itself is required due to microsoft/vcpkg#18718.
Cache is improved, so vcpkg itself is not built every time. Upgrade of vcpkg itself is required due to microsoft/vcpkg#18718.
This could be the issue in bergamot-translator: * microsoft/vcpkg#18718
A cmake change has caused vcpkg to fail without much error message, which is causing windows workflow runs to fail. Details in the following link: * microsoft/vcpkg#18718 To fix, we're going with a version bump in vcpkg. Seeing that run-vcpkg also seems to have gotten an update, updating run-vcpkg from 7.3 to 7.4 Playing with fire: vcpkg master commit
A cmake change has caused vcpkg to fail without much error message, which is causing windows workflow runs to fail. Details in the following link: * microsoft/vcpkg#18718 To fix, we're going with a version bump in vcpkg. Seeing that run-vcpkg also seems to have gotten an update, updating run-vcpkg from 7.3 to 7.4 Playing with fire: vcpkg master commit
Cache is improved, so vcpkg itself is not built every time. Upgrade of vcpkg itself is required due to microsoft/vcpkg#18718.
Describe the bug
vcpkg installquits immediately after printingComputing installation plan.... No package is actually built or installed.It does create 2 empty folders,
installed\vcpkg\infoandinstalled\vcpkg\updates.Environment
To Reproduce
Steps to reproduce the behavior:
.\vcpkg.exe install <any package>Computing installation plan...and quitExpected behavior
vcpkg actually installs the package
Failure logs
I'm not sure how to get failure log. There is no newly created file after running
vcpkg installin vcpkg's directory.The text was updated successfully, but these errors were encountered: