search

nolanderc / glsl_analyzer

Language server for GLSL (autocomplete, goto-definition, formatter, and more)
GNU General Public License v3.0
156 stars 3 forks source link

#include not working in vscode on windows #60

Open deivse opened 1 month ago

deivse commented 1 month ago

When using vscode on windows, using #include results in BadPathName errors in the log. However, when I ctrl-click on one of the paths printed in the errors, vscode succesfully opens the file, so the paths seem to be valid. Interestingly, the susccessfully opened paths in the log all seem to use / as the separator, and the errored paths have \\ in them.

image

nolanderc commented 1 month ago

Could you please include the code snippets thag are failing as well? Are the paths defined with a backslash? Try changing everything to use regular slashes and see if that fixes removes the errors.

deivse commented 1 month ago

Here's the header of the file, I assume everything below shouldn't be important. I'm also using the latest version available in the vscode extension (manually updated today with the download command)

#version 450 core

#include "../common/transform_uniform_block.glsl"
#include "../common/volume_uniform_block.glsl"
#include "../common/util_funcs.glsl"

out layout(location = 0) vec4 FragColor;