-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[vcpkg-tool] vcpkg insist on downloading 7zip #39921
[vcpkg-tool] vcpkg insist on downloading 7zip #39921
Comments
Can you show the log with --debug |
Just a thought, vcpkg might be looking for |
Here you go:
|
In case that helps:
|
After looking at the source code I see that vcpkg always uses an own copy of 7zip and does not search on the path for it |
@MonicaLiu0311 Does this answer your concern ? Apparently this is a confirmed issue, and could be improved. |
@BillyONeal Can you help take a look at this? Ping again. |
This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment. |
Ping |
Can you point the exact line location ? Thanks ! |
Is there any workaround for this? The current 7-zip that is downloaded has some kind of problem and fails to install. This prevents vcpkg from working at all. |
What is "ShimGen"? Does a 7z.exe we can use end up on the PATH?
Can you be more specific as to what "fails to install" means? |
A new version has been released:
|
2025-01-20 was backed out due to a showstopper bug in overlay-ports; reopening |
Describe the bug
This is a docker image with VS BuildTools 2022, cmake, 7z and ninja. However vcpkg insist on download a custom copy of 7zip:
System has it in the PATH:
Environment
To Reproduce
Steps to reproduce the behavior:
For reference
Expected behavior
vcpkg should try harder to use the system installed 7zip.
Failure logs
Additional context
Docker image for windows 2022 was prepared with:
The text was updated successfully, but these errors were encountered: