-
Notifications
You must be signed in to change notification settings - Fork 836
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#include file pathnames are being processed for escapes #2142
Comments
The problem is in |
A quick fix is just setting int scan(TPpToken* t) override
{
pp->disableEscapeSequences = true;
const int result = stringInput.scan(t);
pp->disableEscapeSequences = false;
return result;
} But I'm not sure if it's suitable, but should be good, since it used it 1344454 too. |
What method are you using to get this error? When I try compiling an HLSL shader with a backslash in a header name, it works. |
I'm using this: Interesting fact: when I use shaderc to compile the same shader, it compiles it successfully. |
I grabbed it. |
Note that |
Using the set of files you previously posted and the latest glslang, it successfully compiles the I used the command line |
So, the log wasn't telling the truth about why it really fails? While debugging it, I've found a way to fix the first message about escape sequences with the quick fix I provided above. // common.h, in the end of file:
#define FXPS technique _render{pass _code{PixelShader=compile ps_3_0 main();}}
#define FXVS technique _render{pass _code{VertexShader=compile vs_3_0 main();}} techniques are not supported and probably they are the reason of failure? P.S. I can't modify shaders (including removal of that defines) 🙂 |
Problematic code:
HLSL shader with this:
Expected behaviour
Successful preprocessing and compilation.
Current behaviour:
Preprocessing errors:
glslang version
Built from commit 3bf1dab
Misc
Seems to be related with #2108.
The text was updated successfully, but these errors were encountered: