ThatOSDev

> As far as I can tell, you have to enable this warning explicitly, or use `-Wall`. We don't generally fix `-Wall`-only warnings. > --SNIP-- I should have added my...

> I can post a fix for this one - like Sean said we don't normally worry about -Wall, but I can tweak the code easily enough to avoid the...

> No prob! > > Remember you can do: > > #pragma GCC diagnostic push #pragma GCC diagnostic ignored "-Warray-bounds" #include "stb_image_resize2.h" #pragma GCC diagnostic pop > > In the...

> I just posted the next version that fixes this, but remember you can easily wrap the header to avoid this (see two messages above)... Found your pull request. I'll...

Just to give a bit more info. I have tried to undefine the 4 NULL functions to no avail. I'm using GCC 13.2 ( MinGWx64 ) on windows. FROM HERE:...

> I compile GLFW in Windows with the files added manually to my project, including the `null_` files, and do not have any compile or link errors. > > Could...

Just dawned on me that you are talking about adding files within a file, (UNITY BUILD) kind of like the library RAYLIB does. I have done the same thing with...

Yea the 4 names that clash are : acquireMonitor releaseMonitor createNativeWindow fitToMonitor It shows that they are redefined. Hope this helps.