@Thanatomanic , Iâd like to know how you get on with a Windows build - Iâm a windows user and would like to try vkdt. The Way ForwardâŚ?
Happy New Year everyone!
Package glfw3 was not found in the pkg-config search path.
Perhaps you should add the directory containing glfw3.pc' to the PKG_CONFIG_PATH environment variable Package 'glfw3', required by 'virtual:world', not found Package glfw3 was not found in the pkg-config search path. Perhaps you should add the directory containing glfw3.pcâ
to the PKG_CONFIG_PATH environment variable
Package âglfw3â, required by âvirtual:worldâ, not found
Package glfw3 was not found in the pkg-config search path.
Perhaps you should add the directory containing glfw3.pc' to the PKG_CONFIG_PATH environment variable Package 'glfw3', required by 'virtual:world', not found Package glfw3 was not found in the pkg-config search path. Perhaps you should add the directory containing glfw3.pcâ
to the PKG_CONFIG_PATH environment variable
Package âglfw3â, required by âvirtual:worldâ, not found
make[1]: Entering directory â/home/user/vkdtâ
Makefile:56: [ext (Makefile)]
mkdir -p built/
bin/config.mk.defaults:51: [ext (Makefile)]
bin/config.mk.defaults:51: [ext (Makefile)]
bin/config.mk.defaults:51: [ext (Makefile)]
Package glfw3 was not found in the pkg-config search path.
Perhaps you should add the directory containing glfw3.pc' to the PKG_CONFIG_PATH environment variable Package 'glfw3', required by 'virtual:world', not found bin/config.mk.defaults:51: [ext (Makefile)] Package glfw3 was not found in the pkg-config search path. Perhaps you should add the directory containing glfw3.pcâ
to the PKG_CONFIG_PATH environment variable
Package âglfw3â, required by âvirtual:worldâ, not found
bin/config.mk.defaults:52: [ext (Makefile)]
bin/config.mk.defaults:52: [ext (Makefile)]
bin/config.mk.defaults:52: [ext (Makefile)]
Package glfw3 was not found in the pkg-config search path.
Perhaps you should add the directory containing glfw3.pc' to the PKG_CONFIG_PATH environment variable Package 'glfw3', required by 'virtual:world', not found bin/config.mk.defaults:52: [ext (Makefile)] Package glfw3 was not found in the pkg-config search path. Perhaps you should add the directory containing glfw3.pcâ
to the PKG_CONFIG_PATH environment variable
Package âglfw3â, required by âvirtual:worldâ, not found
Makefile:13: [ext (Makefile)]
Makefile:57: [ext (Makefile)]
make -C ext/
make[2]: Entering directory â/home/user/vkdt/extâ
mkdir -p âŚ/built/ext/rawspeed
cd âŚ/built/ext/rawspeed; cmake âŚ/âŚ/âŚ/ext/rawspeed -DBUILD_TESTING=0 -DCMAKE_BUILD_TYPE=release -DRAWSPEED_ENABLE_LTO=off -DRAWSPEED_ENABLE_DEBUG_INFO=off -DBUILD_BENCHMARKING=off -DBUILD_FUZZERS=off -DBUILD_TOOLS=off
CMake Error at C:/msys64/ucrt64/share/cmake/Modules/CMakeDetermineCXXCompiler.cmake:48 (message):
Could not find compiler set in environment variable CXX:
clang++.
Call Stack (most recent call first):
CMakeLists.txt:17 (project)
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
â Configuring incomplete, errors occurred!
See also âC:/msys64/home/user/vkdt/built/ext/rawspeed/CMakeFiles/CMakeOutput.logâ.
make[2]: *** [Makefile:15: âŚ/built/ext/rawspeed/Makefile] Error 1
make[2]: Leaving directory â/home/user/vkdt/extâ
make[1]: *** [Makefile:57: ext] Error 2
make[1]: Leaving directory â/home/user/vkdtâ
make: *** [Makefile:7: all] Error 2>
heya, nice to see you trying this roel unfortunately i donât know pretty much anything about windows.
there has been this thread and there is a fork trying to build with mingw (but i canât even tell how that relates to msys2). probably something relating to posix dirent is relevant for both cases.
i donât know about ninja, i havenât been using it. maybe thatâs a default/fallback now? this here seems to indicate you should be able to somehow supply -G or set the CMAKE_GENERATOR environment variable and maybe just set it to make?
the build process aside, i expect some compatibility issues on windows, off the top of my head:
src/core/fs.h needs platform specific implementations for standard things like path handling. in particular detecting the full path of the executable is necessary so vkdt can pick up the data and modules directories
in a few places iâm depending on a gnu extension to realpath which also fills in the expanded real path (replacing symlink to directories by the real name) even if the resulting filename does not point to an existing file. probably realpath should have a fs_realpath platform specific implementation too.
vkdt uses symlinks to create collections of tags. probably thereâs no such thing on windows.
oh, it seems you are right. you can tell i havenât used windows for productive work since 2000 or so (reluctantly so). if that works with interface calls like unlink() or symlink() there should be âno problemâ˘â.
Looks like slowly and silently vkdt is taking over the lead. Many tools are still missing but some are already better than in old darktable⌠time fliesâŚ
I was trying from the ucrt terminal as that works nicely with dark table. Should I try clang term instead and also check that the path is set properly??
I will tryâŚthe first thing I really dont ezactly understand are all these options. I assumed each was using a different compiler or well really I donât understand it⌠I just know I had downloaded all the ucrt packages and built DT from that terminal when it was updated to use that⌠but what if I open the clang option here⌠is that going to use clang?? I think I still get the same resultsâŚ
Got it to compile just fine here on Fedora 37, itâs heckin fast on my RX 6900XT. A little different to work with than traditional darktable or RawTherapee.
As for the confusion in environments: itâs all about which standards are used by default, and a little about compatibility. I donât think it matters a lot if youâre just compiling for yourself. More info here: Environments - MSYS2
unfortunately i donât know pretty much anything about windows.
. or so my dad used to say. I will give that a try and see where that leaves me⌠Thx