Open iOrange opened 4 months ago
Could be this issue: https://github.com/microsoft/vcpkg/issues/36103
You could try to update vcpkg and use the latest version of jasper.
Thanks for the info. I'm not familiar with the vcpkg, but I'll try to dig thanks.
For anyone needing to do this, the method that worked for me was to add the following:
CMakeLists.txt, line 22:
# This should be removed once jasper is fixed.
# See https://github.com/microsoft/vcpkg/issues/36103#issuecomment-1888423591
# It requires MSVC 14.37.32822, which can be installed for VS 2022 by
# going to "Individual Components", finding "Compiler, build tools, and runtimes",
# and selecting "MSVC v143 - VS 2022 C++ x64/x86 build tools (v14.37-17.7)(Out of support)"
set(VCPKG_OVERLAY_TRIPLETS "${CMAKE_SOURCE_DIR}/vcpkg-overlay-triplets")
vcpkg-overlay-triplets/x64-windows-static.cmake:
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE static)
set(VCPKG_LIBRARY_LINKAGE static)
set(VCPKG_PLATFORM_TOOLSET_VERSION "14.37.32822")
vcpkg-overlay-triplets/x64-windows.cmake:
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE dynamic)
set(VCPKG_PLATFORM_TOOLSET_VERSION "14.37.32822")
Has anyone tried updating to the latest vcpkg / jasper instead?
I did a git pull origin master
in the vcpkg
directory, but that didn't change anything. I'm assuming the jasper configuration is managed by vcpkg itself?
No, you would have to change the baseline and the jasper minimal version in vcpkg.json
.
See this commit for an example.
System Information
TrenchBroom right from the repo on Windows 11
Expected Behavior
should build
Steps to Reproduce
Clone the repo, make a
build
folder inside, go to it, runcmake .. -G "Visual Studio 16 2019" -T v142 -A x64 -DCMAKE_PREFIX_PATH="d:\Qt\5.15.2\msvc2019_64"
it'll download and build bunch of libraries until it errors:
I wanted to debug to see why my dds textures won't show in the textures browser (they're shown as black square), but can't even build the TrenchBroom.