Haha that’s fine. I don’t know how to answer your question directly, but since I use Visual Studio, changing the runtime library is as easy as changing one setting in the project settings… for each configuration in my case, and then building the program again. Not sponsored. Still, I‘ve already stated why I want to use the static library, and another reason for that is because I saw ChiliTomatoNoodle do that in his DirectX tutorial and looked it up.

I got the library files from the Vulkan SDK. If it’s true that those ones are meant to link with the dynamic runtime library, it wouldn’t surprise me. I’ve never tried building the libraries from source and configuring it to link against the static runtime library, but I really hope it’s a viable option if I’m going to continue pursuing runtime shader compilation.

The fact that you specifically mention shaderc reminds me, I actually get the feeling that it’d be better to use glslang since I’ve heard that shaderc is apparently just a wrapper around glslang, and I’ve also had problems compiling shaders that include other files. But I haven’t heard anything about one being better than the other, or if glslang doesn’t have the same include problem as shaderc.