Add JULIA_VULKAN_LIBNAME for setting a custom libname #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a small part of what I did in #34, related to how the libname is picked. Rather than just hardcoding a value for each platform, it allows one to set a custom libname. I also put a more explicit error message, and removed the use of JULIA_VULKAN_SDK_*. So basically, a libname is chosen at compile time, and checked/dlopened at runtime via
__init__
. Hopefully some of the work of #34 on dynamic library loading will be applicable to 1.6, because it's a pain to change the libname once VulkanCore is compiled (if there are multiple Vulkan implementations you want to test for example, or if you had a bad libname before compiling). I kept a working version of #34 that allows a dynamic loading behavior on >= 1.6 and falls back to what we do now for earlier versions, we can give it a look once 1.6 is out.