Allow applications to specify the Vulkan library path

I don't know if vendoring the Vulkan library is appropriate, but regardless,
this allows applications to set the name to whatever they want, or specify an
absolute path, just in case the standard value baked into Pugl isn't the right
one in some situation.

1 files changed, 14 insertions, 1 deletions

diff --git a/bindings/cpp/include/pugl/vulkan.hpp b/bindings/cpp/include/pugl/vulkan.hpp
index a742085..5bb790d 100644
--- a/bindings/cpp/include/pugl/vulkan.hpp
+++ b/bindings/cpp/include/pugl/vulkan.hpp
@@ -51,7 +51,20 @@ public:
      failed loader, but the accessors will always return null.
   */
   explicit VulkanLoader(World& world) noexcept
-    : Wrapper{puglNewVulkanLoader(world.cobj())}
+    : VulkanLoader{world, nullptr}
+  {}
+
+  /**
+     Create a new dynamic loader for Vulkan functions from a specific library.
+
+     This is the same as the simpler constructor, but allows the user to
+     specify the name of the Vulkan library to load, for certain packaging
+     scenarios or unusual/unsupported system configurations.  The `libraryName`
+     is passed to the system library loading function (`dlopen` or
+     `LoadLibrary`), and supports an absolute path.
+  */
+  explicit VulkanLoader(World& world, const char* const libraryName) noexcept
+    : Wrapper{puglNewVulkanLoader(world.cobj(), libraryName)}
   {}
 
   /**