add boolean preprocessor symbol GRIMOIRE or similar

[elenzil]

add boolean preprocessor symbol GRIMOIRE or similar

[jshrake]

sweet! .. but causes an "unknown error" on shadertoy, even bracketed by #if 0.

#include <any_file.glsl> also works in grimoire and also works in shadertoy when bracketed by #if 0.

[jshrake]

This is a good feature request!

if i were doing it, i'd probably just literally prepend the line #define GRIMOIRE to the front of each shader file, but that seems hackish.

I think that's fine as it produces something fairly simple that's easy to document. I like it.

an alternative approach might be to implement something similar to Shadertoy's common tab, but only functional in grimoire. eg grim_common.glsl.

You can currently #include "any_file_you_want.glsl", but you would need to take into account how this would impact your ability to port the code over to shadertoy :) The path is relative to the grim.toml file.

then one could add whatever #defines one pleased in there. however with a view to establishing a consistent way stuff is done, i'd probably opt for the other approach first.

One feature I've considered is allowing users to specify a set of preprocessor symbols in the pass configuration. This could be useful for reusing the same shader in different ways across multiple passes.

[elenzil]

I think that's fine
cool!

#include "any_file.glsl"
sweet! .. but causes an "unknown error" on shadertoy,
even bracketed by #if 0. example

allowing users to specify a set of preprocessor symbols in the pass configuration
yeah, that could definitely be useful.
i think i'd still consider forcing something for grimoire in there,
just to get folks on the same page w/r/t the symbol, versus making up our own "using_grimoire" "env_grimoire", etc.

[elenzil]

so it does, great!

[jshrake]

Closed by #62. @elenzil, you should now be able to use #ifdef GRIMOIRE in your shader code on HEAD of master.

One feature I've considered is allowing users to specify a set of preprocessor symbols in the pass configuration. This could be useful for reusing the same shader in different ways across multiple passes.

I'm tracking this in #64

[elenzil]

woohoo, this is great!