On Thu, Feb 15, 2018 at 4:35 AM, Timo Aaltonen <[email protected]> wrote: > Looks like latest vulkan changed how it depends on SPIRV, so we'll just > bite the bullet and package glslang and spirv-tools separately instead..
Yes, past the 1.0.65 tag/branch, the loader/layers repository (as well as VulkanSamples) quit keeping track of the embedded explicit git commit for spirv-tools, and now relies on glslang to pull in the correct commit. Still ugly, but slightly less ugly than it used to be (at least now, there's only one place keeping track of that git commit ID, rather than two places). That shouldn't change the packaging very much though, and it has to change anyway to package 1.0.68 regardless. But maybe you're right, and the two should be packaged separately anyway, even though that's going to make keeping versioning straight between all of them messy and manual. Would you like me to file ITPs for them? Or are you planning on doing so right away?
