В Вт, 19/10/2021 в 07:15 +0200, Jiri Slaby пишет:
On 19. 10. 21, 5:51, Dead Mozay wrote:
Hello everyone, Why are the header files in the openSUSE wayland- devel package packed in /usr/include/wayland and not /usr/include as provided by the developers? When building almost any package that requires wayland, an error occurs due to the fact that the header files are not located where they should be. Now ran into this error again, the system vulkan cannot find the header file wayland-client.h Because it looks for it along the path /usr/include/wayland-client.h, and in openSUSE it is located in the path /usr/include/wayland/wayland-client.h I've only seen such a solution in openSUSE, other distributions use default paths Was there any reason for this?
I don't know the reason (maybe potentially conflicting headers with other packages), but it's done properly anyways: $ pkg-config --cflags wayland-client -I/usr/include/wayland
Detection in vulkan is apparently broken. Doesn't it have --with-wayland=/usr/include/wayland or similar config option?
regards,
the problem is not only with vulkan, at the moment I am building the
mangohud package which depends on the vulkan package, I get the error
/usr/include/vulkan/vulkan.h:41:10: fatal error: wayland-client.h: No
such file or directory
It is possible that this is a developer's mistake, but I found the
decision to move the header files into a separate subdirectory only in
the openSUSE distribution, so the error is only with us
this is not an isolated case, the maintainers have to constantly fix
the paths to the wayland-client.h file, and other files from this
package, this is a little annoying and not always easy to fix,
The header files indicate
#include