Vcpkg Failed To Download From Mirror Set

39 views

Skip to first unread message

Selene Bulger

unread,

Jan 8, 2024, 7:54:19 PM1/8/24

to lighpsychcaltong

By default, vcpkg will stop at the first package build failure. This flag instructs vcpkg to continue building and installing other parts of the install plan that don't depend upon the failed package.

You can run vcpkg commands directly from the Developer Command Prompt for Visual Studio or Developer PowerShell for Visual Studio. This also works for the equivalent consoles embedded in the IDE. vcpkg output is localized according to your Visual Studio language. Both ports and artifacts are supported.

vcpkg failed to download from mirror set

Download Zip https://1naphtquequimo.blogspot.com/?vew=2x5M1K

I think it is important to point out here that you have to run this command as an administrator. When you run the command it tries to insert a .props file into the shared MSBuild path for CPP and that will fail without admin privileges: `error: failed to install system targets file to C:\Program Files (x86)\MSBuild/Microsoft.Cpp/v4.0/V140/ImportBefore/Default/vcpkg.system.props `

Error: Building package qt5-base:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at including:
Package: qt5-base:x64-windows
Vcpkg version: 2018.10.20-nohash

Hey,
thanks for your help. After I added to do not try to download QT, it works until the script wants to download icu, which also failed. So I added that as well. Then after a few more attempts, the directory "C:\Users\ME\Win64" seems to get deleted or do never exist on my PC.
Anyway, I've got the compiled binaries now from a classmate and figured out, that the show.exe is not starting via batch file. I've tried to start it with "start "" "%dp0show.exe" -s 0 -e 0 %dp0..\dat\", the program opens and closes directly with no output. Is the command wrong or is the program only startable via normal Shell?

(1) The statement "Debug and Release should both work" in the Link you cite comes from Florian Leutert who is a Windows expert and installed all the dependencies manually himself. In our case, build.cmd only installs the release build of all dependencies with vcpkg so doing a debug build might not work as the debug versions of the dependencies might be missing.

It will in turn call ./scripts/bootstrap.sh script and download the second component - vcpkg CLI tool binary from its repository. In my case it was 2022-09-20 version. It also does some other things, which you can look up in the script file. I would prefer to do all these things myself than letting a script execute a bazillion commands in my system.

But that project also depends on PDFium, which in turn depends on JPEG/jpeg-turbo too, and in our PDFium port we resolve this the same way via vcpkg (having disabled building those from vendored sources). But the problem now is how to specify which JPEG library should PDFium port use (meaning that it is controlled via PDFium port features)?

Unrelated to that, you might have noticed an ololo message being printed out during the installation of dearimgui port (version 1.88.0). That message came from decovar-vcpkg-cmake helper port, which dearimgui port depends on and calls decovar_vcpkg_cmake_ololo() function from.

$ rm -r ./*; rm .ninja*; ls -lah$ cmake -G Ninja -DCMAKE_BUILD_TYPE=Release \ -DCMAKE_INSTALL_PREFIX="../install" \ -DUSING_PACKAGE_MANAGER_VCPKG=1 \ -DCMAKE_TOOLCHAIN_FILE="$VCPKG_ROOT/scripts/buildsystems/vcpkg.cmake" \ ..-- Running vcpkg installFetching registry information from g...@github.com:retifrav/vcpkg-registry.git (HEAD)...Detecting compiler hash for triplet x64-osx...The following packages will be built and installed: dearimgui[backend-glfw,core]:x64-osx -> 1.88.0 -- /Users/USERNAME/.cache/vcpkg/registries/git-trees/c3282e78368406b65f57ef0e3afa7cda2fc26501 * decovar-vcpkg-cmake[core]:x64-osx -> 2022-10-15 -- /Users/USERNAME/.cache/vcpkg/registries/git-trees/4ceb1e31d28a155bcbeb26382478b024a3d82cd3 glad[core]:x64-osx -> 0.1.36 -- /Users/USERNAME/.cache/vcpkg/registries/git-trees/2341f5144ce8e76a256289517d61abb4ab9fb72c glfw[core]:x64-osx -> 3.3.8 -- /Users/USERNAME/.cache/vcpkg/registries/git-trees/597fa07e1afd57c50dfdbeb0c0d28f4157748564 * vcpkg-cmake[core]:x64-osx -> 2022-08-18 -- /Users/USERNAME/.cache/vcpkg/registries/git-trees/84c200e8e625d4d99b1649525fcdf81a73197078 * vcpkg-cmake-config[core]:x64-osx -> 2022-02-06 -- /Users/USERNAME/.cache/vcpkg/registries/git-trees/e23b39e21f0dd42ecc615262640d211c39696aa1Additional packages (*) will be modified to complete this operation.Restored 6 package(s) from /Users/USERNAME/.cache/vcpkg/archives in 74.03 ms. Use --debug to see more details.Installing 1/6 vcpkg-cmake-config:x64-osx...Elapsed time to handle vcpkg-cmake-config:x64-osx: 5.364 msInstalling 2/6 vcpkg-cmake:x64-osx...Elapsed time to handle vcpkg-cmake:x64-osx: 4.532 msInstalling 3/6 decovar-vcpkg-cmake:x64-osx...Elapsed time to handle decovar-vcpkg-cmake:x64-osx: 6.853 msInstalling 4/6 glfw:x64-osx...Elapsed time to handle glfw:x64-osx: 14.2 msInstalling 5/6 dearimgui:x64-osx...Elapsed time to handle dearimgui:x64-osx: 31.32 msInstalling 6/6 glad:x64-osx...Elapsed time to handle glad:x64-osx: 31.76 msTotal elapsed time: 4.212 sglfw provides CMake targets: # this is heuristically generated, and may not be correct find_package(glfw3 CONFIG REQUIRED) target_link_libraries(main PRIVATE glfw)dearimgui provides CMake targets: # this is heuristically generated, and may not be correct find_package(dearimgui CONFIG REQUIRED) target_link_libraries(main PRIVATE dearimgui)glad provides CMake targets: # this is heuristically generated, and may not be correct find_package(glad CONFIG REQUIRED) target_link_libraries(main PRIVATE glad::glad)-- Running vcpkg install - done-- The C compiler identification is AppleClang 14.0.0.14000029-- The CXX compiler identification is AppleClang 14.0.0.14000029-- Detecting C compiler ABI info-- Detecting C compiler ABI info - done-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc - skipped-- Detecting C compile features-- Detecting C compile features - done-- Detecting CXX compiler ABI info-- Detecting CXX compiler ABI info - done-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ - skipped-- Detecting CXX compile features-- Detecting CXX compile features - done-- Found OpenGL: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk/System/Library/Frameworks/OpenGL.framework-- Configuring done-- Generating done-- Build files have been written to: /path/to/glfw-imgui-example/build

Anyway, that was the project itself, but how to build vcpkg-resolved dependencies with Clang as well? As in previous cases, you would need to make a custom toolchain for that and chainload it from a custom triplet.

Installing vcpkg is a two-step process: first, clone the repo, then run the bootstrapping script to produce the vcpkg binary. The repo can be cloned anywhere, and will include the vcpkg binary after bootstrapping as well as any libraries that are installed from the command line. It is recommended to clone vcpkg as a submodule for CMake projects, but to install it globally for MSBuild projects. If installing globally, we recommend a short install path like: C:\src\vcpkg or C:\dev\vcpkg, since otherwise you may run into path issues for some port build systems.

I installed llvm from vcpkg, and then when I execute "cargo run", it reports an error, saying it can find libclang.dll, but LoadLibraryExW failed.I then dumpbined the libclang.dll, it outputs is exported functions just fine.