I haven't released 1.9 yet.
While perfectly useable, the idea with my xBRZ implementations is mainly to demonstrate a proof of concept to dismiss excuses of project maintainers like "too much work, too difficult, not possible". But in the long run each project would have to decide for itself if it wants to integrate xBRZ. Personally I don't see why not, because all those projects support HQx, which is in all respects inferior to xBRZ. So the best approach to get an updated xBRZ would be to directly ask the maintainers of MAME...
The file name is correct, it's a 32-bit executable.
Fine with me!
I think I forgot! :D Just updated the latest source code (which is still ScummVM 2.0) to use the FFS task scheduler. The build now requires an additional file, thread.cpp, which is part of FreeFileSync. Caveat: I haven't tested the code! I couldn't even compile it, since ScummVM apparently doesn't support Unicode on Windows. On macOS/Linux this shouldn't be a problem. You just have to make sure that thread.cpp (and its dependencies e.g. sys_error.cpp, ect.) are compiled and linked against ScummV...
I think I forgot! :D Just updated the latest source code (which is still ScummVM 2.0) to use the FFS task scheduler. The build now requires an additional file, thread.cpp, which is part of FreeFileSync. Caveat: I haven't tested the code! I couldn't even compile them, since ScummVM apparently doesn't even support Unicode on Windows. On macOS/Linux this shouldn't be a problem. You just have to make sure that thread.cpp (and its dependencies e.g. sys_error.cpp, ect.) are compiled and linked against...
You're not offending at all. I'm just busy with different things, that's all.
Funny how small open source devs seem to care more about licenses than the "big guys" (cough Nintendo cough) https://twitter.com/lunasorcery/status/1242569546038460416