Repository navigation
Replies: 2 comments 10 replies
|
You'll have to build it youself for the moment, builds won't migrate to SDL3 for a while, honestly there's nothing interesting in the SDL3 backend, both backends are virtually equal, SDL2 being more stable for obvious reasons, I've been using the SDL3 backend for a while but only on Linux, and haven't tested in any other OS, although it should work as normal. Maybe you can try to build it on Windows. One extra detail is that eepp brings some helpers to auto install the SDL2 library, but for SDL3 that currently does not exists. I merged the branch since its working for me but probably needs more work, and also I did not manually port it because was tremendously boring, this was 95% AI agents which a don't usually do, but for these kind of things they are good enough, I avoided the boring parts since this is not a fun project for me. |
|
The SDL2 MojoAL is selected even though the backend is SDL3. What it should pick is the recently added MojoAL-SDL3. Please fix the logic in your |
|
Even after disabling MojoAL with |
|
Oh, I found the issue. The system doesn't have SDL2, nor did I tell the build script to download SDL2 for me. SDL3 is obviously picked as the backend. But that is not enough. We need to explicitly set the backend to SDL3 with |
|
You should fix MojoAL-SDL3. It has a ton of compilation errors. |
|
Errors or warnings? Compiles just fine, if there are warnings they are not my responsibility |
|
Errors. It stops the build process. Which platforms have you tested it? Try on more platforms than just Linux. |
|
It seems that mojoAL isn't compiling in Windows in the oficial repo, but I fixed it in eepp, so now it should work for you. |
|
Thank you. |
Uh oh!
There was an error while loading. Please reload this page.
Current builds are still SDL2. SDL3 is just merged and closed. I'm very excited to try it out.
All reactions