I don´t think there any for Fedora… plus this way you only need to provide 1 package for all the platforms!
well for fedora someone would need to tell us why it doesnt find the OMP library. the same buildrequires work for darktable.
as you see it tries to build it Show graphics:darktable:master / vkdt - openSUSE Build Service
oops sorry it seems i broke thumbleweed too. that’s the same issue with the base patch as we discussed last time. it should be a patch of config.mk against /dev/null to be future proof.
fwiw i think this would be a good config.mk:
VKDT_USE_FREETYPE=1
export VKDT_USE_FREETYPE
VKDT_USE_RAWSPEED=1
export VKDT_USE_RAWSPEED
VKDT_USE_EXIV2=1
export VKDT_USE_EXIV2
VKDT_USE_V4L2=1
export VKDT_USE_V4L2
VKDT_USE_MLV=1
export VKDT_USE_MLV
VKDT_USE_ALSA=1
export VKDT_USE_ALSA
# VKDT_USE_FFMPEG=0
# export VKDT_USE_FFMPEG
CC=clang
CXX=clang++
GLSLC=glslangValidator
OPT_CFLAGS=-Wall -pipe -O3 -march=x86_64
OPT_LDFLAGS=
AR=ar
RAWSPEED_PACKAGE_BUILD=1
export CC CXX GLSLC OPT_CFLAGS OPT_LDFLAGS AR RAWSPEED_PACKAGE_BUILD
I don’t know if it’s related. On my desktop (debian sid) I don’t see any build issue but at run time time vkdt doesn’t see libomp (or seems to). While on my laptop (debian sid) and same libraries, vkdt works (and BTW contrast/radius has some effect now).
Other topic, on my laptop, with a bluetooth mouse and the touchpad as well, the zoom is not stable. Any further mouse movement resets it. Anyone has this issue ?
i’ve seen this happen when the shaders run into a timeout on super slow gpus. sounds plausible on older laptops, though i don’t know your hardware.
OK, understood. The laptop runs the integrated Radeon. Thanks
… you can try to set lod in your ~.config/vkdt/config.rc by putting intgui/lod:4 or some value > 1 to reduce the load.
I am not sure that’s so simple because of Vulkan/GPU acceleration. I mean there is no Appimage for darktable either and there must be a good reason for that. Afaik the flatpak cannot use the GPU.
That improves a bit the zooming process but it still go away when moving the mouse. However vkdt seems to be less stable.
When exiting it doesn’t finish and config.rc is not written (null lenght).
hmm interesting. the lod is not really a feature i test much, so i’m not surprised it has issues. might need to investigate nontheless.
you can run with ./vkdt -d all to see any timeout complaints on the console, whether they still persist.
for context: it will process the image at reduced resolution in dr mode. lod=2 should process at exactly the darkroom mode resolution (much like dt does) and anything larger would reduce even more.
I will have a look at Fedora but I need a bit time for that because I will need to set it up.
1 Like
tumbleweed is back.
1 Like
ok we figured out why finding openmp failed for fedora. close to fixing the build.
Well, on Fedora 35 I get this error:
clang-13: error: linker command failed with exit code 1
This the whole terminal output between [100%] Built target fuzzers and the end/error:
fedora_compile.txt (38.6 KB)
you will need libomp and libomp-devel on top of clang/clang-devel/llvm-devel
I think I have those.
you can watch our builds here if you are curious 
Show graphics:darktable:master / vkdt - openSUSE Build Service
llvm-devel was missing, apparently
Do you mean that the order in which I install the dependencies matters?
naw. but one would expect that clang-devel pulls libomp-devel. and that libomp-devel would pull libomp. but all those things do not happen automatically. right now it fails with missing debug files. i will check later if the make file strips the binaries already. (it shouldnt do that)
it seems fedora links with “-s” even if it shouldnt.