https://bugs.freedesktop.org/show_bug.cgi?id=109807
Bug ID: 109807
Summary: Add more granular multiarch usage for Mesa Vulkan
overlay JSON manifest
Product: Mesa
Version: git
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Vulkan/Common
Assignee: mesa-dev@lists.freedesktop.org
Reporter: shtetl...@gmail.com
CC: airl...@freedesktop.org, chadvers...@chromium.org,
dan...@fooishbar.org, ja...@jlekstrand.net
After recent changes, VkLayer_MESA_overlay.json references implicit
libVkLayer_MESA_overlay.so which supposedly should be accessible to the loader
(either in common library cache or through LD_LIBRARY_PATH).
It would be better for it to use explicit reference, similar to how actual
Vulkan ICD manifests are doing it. But for that, there should be separate JSON
loader manifest for each architecture. Is it currently possible?
Actual ICDs do support it, i.e. you can find:
/usr/share/vulkan/icd.d/radeon_icd.i686.json
/usr/share/vulkan/icd.d/radeon_icd.x86_64.json
So loader knows which one to pick depending on the arch even during implicit
loading.
Would it work for layers?
I.e. for example:
/usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.i686.json
/usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.x86_64.json
Each of them referencing explicit .so location? Or that requires fixing the
layer loading logic first?
I also opened this to be able to load layer JSON explicitly, like ICD manifests
allow:
https://github.com/KhronosGroup/Vulkan-Loader/issues/154
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
