Arch Linux User Repository

My system is updated, upgraded and rebooted, but there's something in my build pipeline that insists on trying to include c++/13* for some reason. Managed to work around it by just manually editing the Makefiles after a failed build for now. Since it's apparently a me problem, I'll look more into fixing it soon(tm)

marza, update your system, I built it on different PCs and everything is perfectly assembled and working.

<command-line>: fatal error: /usr/include/c++/13*/limits: No such file or directory
compilation terminated.
make[2]: *** [Makefile.Release:330: release/abstractserver.o] Error 1
make[2]: Leaving directory '/home/martin/moonlight-qt/src/qmdnsengine'
make[1]: *** [Makefile:42: release] Error 2
make[1]: Leaving directory '/home/martin/moonlight-qt/src/qmdnsengine'
make: *** [Makefile:564: sub-qmdnsengine-release] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

Not sure if this is an issue with dependencies of this package, the github repo, or my setup? I only have 14.2.1 in /usr/include/c++. Tried to install gcc13, but limits from that package ends up in /usr/lib/gcc/x86_64-pc-linux-gnu/13.3.0/include/c++/limits. I guess I could symlink it, but that seems like a dirty solution.

EDIT: btw, the include is generated into /home/martin/moonlight-qt/src/qmdnsengine/Makefile.Release, but I don't know enough about (q)make to understand how this file is created.

you should increment pkgrel when non-specified build dependencies(e.g. libplacebo) change their versions, so chaotic-aur builds a new package OR specify build dependencies OR make a patch that forces build system to link against symlink to actual library version

P.S. Writing as a comment bc the nature of package being out-of-date seems more like a bug, than maintainer not noticing an update yet

if you get error message after system update:

moonlight: error while loading shared libraries: libavcodec.so.XXX: cannot open shared object file: No such file or directory

just reinstall app:

yay -Rncsu --noconfirm moonlight-qt; yay -Syyu --noconfirm moonlight-qt

I think you don't need to specify many packages, because acceleration already works in Nvidia and AMD/ATI. But at intel, people may not know which package to install for acceleration. I repeat once again, this was added before me. I just added intel-media-driver to optional dependencies after your post. This is done for convenience

Friends, I am grateful for the advice. but! Now let's write strictly to the point. If something doesn't work, suggestions for improvement, etc.

I don't want to sound angry. I just think it should be consistent.

Or maybe there is an official meta package listing every accelerating package as optional dependency?

But I think that doesn't exist and instead every package at that wiki page should be listed as optional.

libva-intel-driver was added even before I became the maintainer of this package

If you added libva-intel-driver to the optdeps why not intel-media-driver as well?
Or the other ones listed here?
https://wiki.archlinux.org/title/Hardware_video_acceleration

Also libva-intel-driver is deprecated by intel-media-driver.