Provide SONAME for libVkLayer_obs_vkcapture.so and libobs_glcapture.so about obs-vkcapture

[nowrep]

There is no need for SONAME since nothing links against these libraries. They are used just as a "plugin".
You can move the Vulkan library anywhere you want, as long as you update the paths in the layer file (json). You can't easily move the OpenGL library.

[AdelKS]

The Gentoo QA seems to say this about plugins

Note that this warning only applies to shared libraries that you would link against. It certainly does not apply to plugins that you would dynamically load. However, plugins should not exist in the main library directory, but rather an application specific subdirectory in the library directory. In other words, it should be /usr/lib/app/plugin.so rather than /usr/lib/plugin.so.

Anyway, I only wanted to bring this to your attention, you can close the issue if you do not plan on doing anything about it.

Thanks!

[nowrep]

Where does this package installs the libraries? https://packages.gentoo.org/packages/media-libs/vulkan-layers
On Arch it gets installed to /usr/lib, and I don't really see any problem with that.

[AdelKS]

They are installed at the same place

➜  ~ equery files vulkan-layers | grep .so
/usr/lib/libVkLayer_khronos_validation.so
/usr/lib64/libVkLayer_khronos_validation.so

But they provide a SONAME and the QA notice does not get triggered

➜  ~ objdump -p /usr/lib/libVkLayer_khronos_validation.so | grep SONAME
  SONAME               libVkLayer_khronos_validation.so
➜  ~ objdump -p /usr/lib64/libVkLayer_khronos_validation.so | grep SONAME
  SONAME               libVkLayer_khronos_validation.so

Although they do not have a version, so not useful anyway ? I checked the ebuild, and the soname is not enforced, it looks like it's setup upstream.

This looks like nitpicking from my part, I am not knowledgeable with all this, I read about it as I opened this issue. It looks like we can safely ignore this since these libs will not be linked against anyway.

Adel