Proc macro for running picasso and include!ing the compiled shader
#22
Conversation
|
yeah this works, i guess, even if the filesystem access is not ideal. also beware that there may be two shaders with the same name i used syn instead of manually parsing but yeah as for the picasso port... I'll do my best, although converting accurately idiomatic C++ to idiomatic Rust isn't super simple. Its data types are all over the place as well. as for naming, i liked |
Export as pub mod macros, add tests, and refactor error handling a bit to make the logic simpler.
Use map_err everywhere to add context / file paths when possible. Also add some basic compile_fail doctests for missing / bad syntax shader sources.
|
I decided to call this I'm not necessarily expecting too much feedback here, but I think I'll plan to merge this after a bit if there isn't any major objection to this API. Having a proper assembler like discussed above would be nice, but this works for now and seems to me a cleaner user experience than the build scripts we had before. |
ian-h-chamberlain
changed the title
ian-h-chamberlain
changed the title
include!ing the compiled shader
|
yeah, i've kinda paused development, been a bit busy with irl stuff and uni, but i do plan to finish what i started |
#2
@adryzz This is what I was thinking about in my comments on that issue. As far as I can tell it works correctly, with perhaps the exception that I haven't tried publishing it to https://crates.io.
My guess is that rewriting
picassoin rust will probably take a bit, so maybe we could just use this in the meantime as a stopgap until the full "librarified" proc macro is available? In any case, users ofcitro3dcould use whichever they prefer.Open to suggestions on naming.
pica200seems to be available on https://crates.io but maybe is a little too general, not sure...