Add option to not remove \n for easier debugging.

[wrightwriter]

If new line characters are stripped, shader errors (on windows/nvidia) become very hard to track.

I propose an option --no-remove-newline, which would allow easier spotting of issues.

[LeStahL]

--format indented

[wrightwriter]

hm, i thought it's not that option, because --format <text|indented|c-variables|c-array|js|nasm|rust> seems unrelated to the preprocessing.

[eldritchconundrum]

For most formats, newlines and indentation can be preserved in the source code of the surrounding language, but are not preserved at run-time, the shader source itself is fully compressed.

--format indented is different. It preserves newlines and indentation in the shader source itself.

It's a bit confusing, I guess... When generating C/JS/nasm/Rust, there's currently no way to preserve newlines and indentation in the shader source itself.

[therontarigo]

For every format option we could have a -indented flavor, which would keep the spaces and newline escapes within the string literals.

It shouldn't be needed though, since a shader may be easily loaded from file for testing purposes, and glslang can catch most errors at project build time.

[wrightwriter]

It can be loaded from file, but my engine has a whole build system around it, which involves shader_minifier, so it's a bit complicated. I'll end up generating the c strings myself, but at that point - it could be a feature of shader minifier. It does already exist to some extent.

Glslang is a valid option... It fared pretty well in my vulkan engine. But it adds complexity to the project.

[LeStahL]

or you could use an incbin type of mechanism, which enables using the plain text formats in both debug and release builds.