Bloodbat
Bloodbat
> * and gcc 14 on windows has a runtime bug or missing feature I compile my local Windows builds with GCC 14 (14.2.0 to be precise; but I've upgraded...
I can't say for sure, but it's unlikely: my local builds use msys' february mingw; the toolkit uses a january commit of crosstool-ng. Maybe... just maybe, updating crosstool to an...
I don't know if this is helpful or useful; but the previous crosstool version 1.26.0, with GCC 13.2 builds a working plugin.
Thank you for the insights :) Looking forward to the Rack 3 implementation. In the mean time, would the removal of the `-static-libstdc++` flag be transparent for developers and, most...
I built a version of my test plugin for Windows without the -static-libstdc++ flag using Docker and, while Rack no longer crashes when opening the browser, the test plugin fails...
My local build is compiled using GCC 14.2.0-3; looking at the official build's strings, Rack is built using GCC 14.2.0-2... toolchain built plugins crash both; plugins built using my local...
I just tested building a plugin with the fix, and I'm happy to report Rack did not crash :) Thanks :)
I wanted to keep them separate; but if it's better to have them together, I'll do it. 2 Questions: Considering the plugins have different slug names, would merging them cause...
Hello! This is the other half of my module collection, for your consideration :) https://github.com/Bloodbat/SanguineMonsters 2.2.0 88b89a46bd66eabfff77929a2b265ab4819c6532 Thanks!
New version, supersedes 2.2.0, for your consideration. https://github.com/Bloodbat/SanguineMonsters 2.3.0 60fffaaec8f9b48d443e284ccb3a6c1191597b03 Thanks :)