Closed GREAT-DNG closed 7 months ago
See #36502
@FrankXie05 Could you specifically indicate what in that issue should help me?
See #36502
@FrankXie05 Could you specifically indicate what in that issue should help me?
MSYS2 removes older library tools after a certain amount of time, and vcpkg is updated, in this case this library was update in May 2023.
To fix in classical mode:
cd <vcpkg-root>
git pull
.\vcpkg-bootstrap.bat
.\vcpkg upgrade --no-dry-run
In manifest mode I am not sure of the exact steps but it would be similar to classic mode, then you would need to re-establish your baseline.
You may also want to look into asset caching.
Hope this helps.
MSYS2 removes older library tools after a certain amount of time, and vcpkg is updated, in this case this library was update in May 2023.
@StarGate-One, I understand, but the problem is that I need exactly it, I'm trying to build Vircadia, there is a possibility that there will be build problems with the new version. Is it possible to install it manually by simply specifying the archive? And where can you get this archive in this case?
To fix in classical mode...
This did not help, here are the outputs of the commands:
> git pull
Already up to date.
vcpkg-bootstrap.bat
was missing, I think it was just renamed:
> bootstrap-vcpkg.bat
Downloading https://github.com/microsoft/vcpkg-tool/releases/download/2022-06-17/vcpkg.exe -> C:\Users\User\VCPKG\8656fb1e\vcpkg.exe... done.
Validating signature... done.
> vcpkg upgrade --no-dry-run
All installed packages are up-to-date with the local portfiles
In manifest mode I am not sure of the exact steps but it would be similar to classic mode, then you would need to re-establish your baseline.
I encountered vcpkg for the first time and I don’t quite understand how to implement it, can you describe in more detail?
You may also want to look into asset caching.
As far as I understand, the cache is built on packages received from MSYS2, but what if it is no longer there?
I also noticed that the script passes additional parameters to vcpkg, perhaps this matters:
--vcpkg-root C:\Users\User\VCPKG\8656fb1e install --triplet x64-windows hifi-client-deps
Extract them to vcpkg\downloads
and rename them to end with *.pkg.tar.zst
msys2-msys2-runtime-3.4.10-4-x86_64.pkg.tar.zip msys2-mingw-w64-x86_64-pkgconf-1~2.1.0-1-any.pkg.tar.zip
@FrankXie05 Bad idea, and completely missing the point.
Unless a user has the full set of old msys2 packages, the user shall use the latest vcpkg. Only the HEAD of vcpkg receives updates/fixes. Everything else will lead from one problem to another. In particular when ignoring msys2 ABI and dependency issues.
For using non-HEAD versions of ports, there is manifest mode, and there are overlay ports.
Extract them to vcpkg\downloads and rename them to end with *.pkg.tar.zst
@FrankXie05 I unpacked it and they already had the required extension. But this had no effect.
For using non-HEAD versions of ports, there is manifest mode, and there are overlay ports.
@dg0yt Judging by the fact that the vcpkg.json
files are present and most likely in use, the manifest mode is already in use. But what are overlay ports and how can you use it to solve the problem?
To fix in classical mode:
cd <vcpkg-root>
git pull
.\vcpkg-bootstrap.bat
---> should have been .\bootstrap-vcpkg.bat
.\vcpkg upgrade --no-dry-run
.\vcpkg-bootstrap.bat
---> should have been.\bootstrap-vcpkg.bat
@StarGate-One I already mentioned this
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.
Operating system
x64-windows
Compiler
MSVC 19.29.30154.0
Steps to reproduce the behavior
Failure logs
Additional context
Package: bullet3[core]:x64-windows -> 3.22
vcpkg-tool version: 2022-06-17-9268e366206712e38102b28dbd1617697a99ff2e vcpkg-scripts version: cef0b3e 2022-06-20 (1 year, 8 months ago)