Not building, whichever version, always the same error :
In file included from /work/build/pcsx2/src/pcsx2/pcsx2/GS/Renderers/Vulkan/VKShaderCache.cpp:19:
/usr/include/shaderc/shaderc.hpp:173:7: error: use of undeclared identifier 'non_sematic_debug_info'; did you mean 'non_semantic_debug_info'?
173 | non_sematic_debug_info);
| ^
/usr/include/shaderc/shaderc.hpp:171:48: note: 'non_semantic_debug_info' declared here
171 | void SetGenerateDebugInfo(bool enabled, bool non_semantic_debug_info) {
| ^
/work/build/pcsx2/src/pcsx2/pcsx2/GS/Renderers/Vulkan/VKShaderCache.cpp:114:32: error: too few arguments to function call, expected 2, have 0
114 | options.SetGenerateDebugInfo();
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/usr/include/shaderc/shaderc.hpp:171:8: note: 'SetGenerateDebugInfo' declared here
171 | void SetGenerateDebugInfo(bool enabled, bool non_semantic_debug_info) {
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/work/build/pcsx2/src/pcsx2/pcsx2/GS/Renderers/Vulkan/VKShaderCache.cpp:116:12: error: no member named 'SetEmitNonSemanticDebugInfo' in 'shaderc::CompileOptions'
116 | options.SetEmitNonSemanticDebugInfo();
| ~~~~~~~ ^
3 errors generated.
From a clean chroot.
Pinned Comments
eclairevoyant commented on 2023-06-18 14:48 (UTC) (edited on 2023-06-18 15:46 (UTC) by eclairevoyant)
This package will track nightlies until the next stable release, as that is what upstream supports and the last stable release is 3 years ago.
I'll try to keep up as much as possible with upstream, but realistically releasing an update every few hours is not happening, especially if I'm going to be checking that it builds properly as one should. Most likely I will only be pushing new versions on weekends.
So, expect once or twice-weekly updates. OOD flags will be removed, just comment if there is a build issue.
Also a reminder: if there are issues specific to this package (i.e. you tested the official AppImage and the issue is not present in the AppImage), report them here. This shouldn't happen often as I will try to maintain deps and flags in accordance with the upstream CI.
If you find an issue with both this package and the AppImage, then report it upstream. If you haven't tested the AppImage... test the AppImage.
Standard caveats and guidelines about AUR also apply:
Read the wiki
There is no support for non-Arch distros or AUR helpers
Always build in a clean chroot before reporting build issues