Michiel Sikma
Michiel Sikma
The readme really should be updated. Right now the website displays instructions that just don't work, or at least not for everybody.
Hi @nick7inc. Thanks for your comment. I'm gonna be honest: I'm not really much of a C programmer, besides a few small experiments. The only thing I did for this...
I don't actually understand where this file and that function are supposed to go. Is there any chance you could make this into a PR?
Is it a matter of adding `include_directories(${ALLEGRO_INCLUDE_DIR})` to the BUILD_ALLEGRO4 statement? That seems to work.
Oh, I just realized also that the following line in `cmake-scripts/FindAllegro4.cmake` might be problematic: ``` exec_program(allegro-config ARGS --libs OUTPUT_VARIABLE ALLEGRO_LIBRARY) ``` If I'm linking to an Allegro library somewhere else,...
I'm not sure if it's necessary to have `allegro-config`. As far as I can tell, just setting the `$ALLEGRO_LIBRARY` manually is sufficient, so it's possible to just check if that...
Is there any chance that Mac builds could be made to support 10.14? Or is there something specific that requires 10.15 at minimum?
I just tried the regular Mac build. Seems to run fine on 10.14. 🙂 For some reason the CRT-Royale and GTU shaders have no output, and I wasn't able to...
Would it be sufficient to just add the option to use a glob pattern for input, and a target directory for output? The caveat would be that you cannot pass...
I'm a bit busy lately... I'm not sure I'll be able to do this for a while unfortunately. Maybe in the future.