Skip to content
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 not working in vscode on windows #60

Open
deivse opened this issue May 21, 2024 · 4 comments
Open

#include not working in vscode on windows #60

deivse opened this issue May 21, 2024 · 4 comments

Comments

@deivse
Copy link

deivse commented May 21, 2024

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
Copy link
Owner

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
Copy link
Author

deivse commented May 21, 2024

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;

@nolanderc
Copy link
Owner

@deivse could you try compiling and testing #65 to see if it fixes you issue. I don't have access to a windows machine at the moment unfortunately...

@deivse
Copy link
Author

deivse commented Jul 31, 2024

Hello, I won't have access to my windows machine for a couple more days, but I'll try to find some time to test once I get back. Thank you for reaching out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants