Search Criteria
Package Details: vulkan-low-latency-layer 0.1.0-3
Package Actions
| Git Clone URL: | https://aur.archlinux.org/vulkan-low-latency-layer.git (read-only, click to copy) |
|---|---|
| Package Base: | vulkan-low-latency-layer |
| Description: | Implicit Vulkan layer that reduces click-to-photon latency for AMD and NVidia. |
| Upstream URL: | https://github.com/Korthos-Software/low_latency_layer/ |
| Licenses: | MIT |
| Submitter: | patlefort |
| Maintainer: | patlefort |
| Last Packager: | patlefort |
| Votes: | 10 |
| Popularity: | 9.75 |
| First Submitted: | 2026-05-17 15:00 (UTC) |
| Last Updated: | 2026-05-18 11:11 (UTC) |
Dependencies (6)
- glibc (glibc-gitAUR, glibc-eacAUR, glibc-git-native-pgoAUR)
- libgcc (libgcc-snapshotAUR)
- libstdc++ (libstdc++-snapshotAUR)
- cmake (cmake3AUR, cmake-gitAUR) (make)
- vulkan-headers (vulkan-headers-gitAUR) (make)
- vulkan-utility-libraries (vulkan-utility-libraries-gitAUR) (make)
Latest Comments
1 2 Next › Last »
HurricanePootis commented on 2026-05-19 05:46 (UTC)
@Luhas On Vanilla Arch, nothing ever should be installed in
/usr/local. Arch does not use/usr/localat all, especially for AUR packages.Lukhas commented on 2026-05-18 23:22 (UTC) (edited on 2026-05-18 23:25 (UTC) by Lukhas)
To be clear, the output of
cat install_manifest.txtwas for the package built from agit cloneand installed withmake install, not from this PKGBUILD. I was comparing the outputs between the two installation methods (make installand AUR).In doubt I tried again, and go figure: I deleted the package and reinstalled it with the original PKGBUILD, and now it works. Vanilla Arch, didn't have anything in my env (I just checked again to be sure). I was using
yayto install the package. Seems like there were gremlins toying around my system...patlefort commented on 2026-05-18 23:02 (UTC)
I'm setting
-DCMAKE_INSTALL_PREFIX=/usr, I don't know how on your system it would still go into/usr/local. Looks like a very broken system. Check what you have in your environment (setcommand) and yourmakepkg.conf. Are you using Arch or a derivative?Lukhas commented on 2026-05-18 22:10 (UTC)
The current package build does build fine on my system, but the resulting package doesn't work, likely due to the files being in the wrong path.
It works if I modify the PKGBUILD as such, adding
-DCMAKE_INSTALL_LIBDIR=lib:Lukhas commented on 2026-05-18 22:09 (UTC)
The current package build does build fine on my system, but the resulting package doesn't work, likely due to the files being in the wrong path.
It works if I modify the PKGBUILD as such, adding
-DCMAKE_INSTALL_LIBDIR=lib:patlefort commented on 2026-05-18 11:13 (UTC)
I've compared the builds with and without glslang and shaderc and there is no difference.
HurricanePootis commented on 2026-05-17 23:51 (UTC)
(Sorry for the spam comments). While not a strict makedepends, whenever I build this package in
extra-x86-64-build -cin a clean chroot, CMake says:Therefore, I think
glslangandshadercshould be added tomakedepends().HurricanePootis commented on 2026-05-17 23:26 (UTC)
I think you should add it. It's something I do in all of my packages that have this issue. And, if you think about it, this flag is automatically added whenever this software is compiled with the Release profile. But, that's just my two cents 🐥🐥🐥
patlefort commented on 2026-05-17 23:19 (UTC)
It's not clear if I should set it here. From the wiki, they mention the issue but don't mention if I should add the flag. Personally I set it in my makepkg.conf.
HurricanePootis commented on 2026-05-17 20:09 (UTC)
@patlefort Thank you for accepting my suggestions! I got one more (lol). I suggest to add
-DNDEBUGto-DCMAKE_CXX_FLAGS="${CXXFLAGS} -DNDEBUG"so that there are no references to the build directory left in the built binary (the warning you get when the package is compressed):1 2 Next › Last »