bret curtis <psi...@gmail.com> wrote: > > One thing I noticed is that upstream integrated their own fork [1] of > > glslang directly into the build [2] as of 1.0.3 [3]. > > Indeed, I created an issue to track this and Robert is aware of the > situation. AnyOldName3 and myself are working together with upstream > glslang that would make it findable and work correctly via cmake so that > cmake itself would not have to carry its own vulkan and glslang files. [1]
Apologies, I somehow missed your Github issue. Looks like you're about 10 steps ahead of where I was when I wrote the email! :) > > I see a few options: > > > > 1) We work with upstream to unvendor the dependency > > > > We are already doing this. :) The trickle down should be happening now. [2] > > > > 2) We disable the shader compiler part of vsg > > > > Please no; while this would get the package into Debian faster it would be > useless for OpenMW, or specifically the Vulkan work we are doing there > which makes use of VSG's glslang. > > > > 3) We patch the build to depend on Debian's glslang package > > > > If we can't wait for 1 to trickle down into Debian's repo; this is a way > forward. I have a branch I've been working on that would resolve that. [3] Agreed - 1 makes most sense to me as well. I have a few machines with different configurations, so feel free to mail me if it would help for me to test against your branch (or anything else for that matter). Thanks, Matthew
