Ryan C. Gordon
Ryan C. Gordon
Let's make sure we undef that after the include, if we defined it, but otherwise I say we try this approach.
Most of the backend APIs either accept float or prefer it, so moving that first is probably good, as we're likely going to be working in floats no matter what...
I think we're going to keep the flags, since we need them in a few non-GPU bits of the library.
> OpenSLES needs to be fixed real quick This isn't true after all, it handles it correctly outside that code snippet.
(Removed UWP from title since WinRT support is gone in SDL3.)
I think we're going to pass on this one.
To be clear, you're just looking to link against something that looks like SDL but isn't actually SDL, to make the builds simpler and avoid revision control bloat. Not looking...
Actually, it sounds like you're looking for that second thing. I think you should probably aim for the first thing, but the second thing is probably doable by adapting SDL's...
> Why should I prefer this being in shared library form, and not just compiled into my application? If you just want to have a simple .c file for your...
> why separation of depth stencil state? This would work on metal Metal was my starting point for designing this, specifically because I think it's the most app-friendly (at least...