Shipping applications include the Vulkan-Loader as well as drivers/layers inside the bundle. They do want or need to find manifests outside of the bundle. Users who have installed the Vulkan SDK globally may find that the layers & drivers used aren't what they expect due to the loader finding these external manifests.
The new env-var's name could be VK_LOADER_SEARCH_ONLY_IN_BUNDLE
Is this specific to a single platform?
macOS/iOS/tvOS/ & similar
Additional context
This is to provide a way to workaround a nuisance warning MoltenVK generates when an app includes MoltenVK in its bundle and there is a system installed MoltenVK.
The warning in question:
"objc[34668]: Class MVKBlockObserver is implemented in both /Users/mark/Projects/khronos/github/KTX-Software/build/macos/Debug/vkloadtests.app/Contents/Frameworks/libMoltenVK.dylib (0x1169466c8) and /usr/local/lib/libMoltenVK.dylib (0x116e366c8). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed."
Shipping applications include the Vulkan-Loader as well as drivers/layers inside the bundle. They do want or need to find manifests outside of the bundle. Users who have installed the Vulkan SDK globally may find that the layers & drivers used aren't what they expect due to the loader finding these external manifests.
The new env-var's name could be
VK_LOADER_SEARCH_ONLY_IN_BUNDLEIs this specific to a single platform?
macOS/iOS/tvOS/ & similar
Additional context
This is to provide a way to workaround a nuisance warning MoltenVK generates when an app includes MoltenVK in its bundle and there is a system installed MoltenVK.
The warning in question: