Closed Swoorup closed 1 year ago
Hi @Swoorup ! Sorry, what do you mean by "making this work"? I use Shader languages support for VS Code extension for example and as you can see, it's linting correctly my shader files:
Hi @Swoorup ! Sorry, what do you mean by "making this work"? I use Shader languages support for VS Code extension for example and as you can see, it's linting correctly my shader files:
Yeah not a question. Just a tip to using the extension I linked. Afaik that extension only supports hlsl linting/validation? The one I linked uses glslLangValidator
. The include
statement doesn't work without requiring the extension
Got it, thanks! I would say, if you have a chance to chose, I would go with "Shader languages support for VS Code" since from what I see on the marketplace, their readme claims this extension should work with HLSL
, GLSL
and Cg
shaders and I haven't had any problems using it with WebGL. However, you might consider installing WGSL if you need to work with WebGPU. I haven't tested it deeply myself though.
I have found that you can make this work with https://marketplace.visualstudio.com/items?itemName=dtoplak.vscode-glsllint
Just use the following script replacing the
script_to_run
to path to glslangValidator. Only downside is that all errors are printed 2 lines below.