A small test of CLib4 and the latest public version of SDL2
Chocolate Quake
"..This port is for purists: no fancy enhancements, no modern effects, just Quake as it was. If you're looking for visual upgrades or modern features, this may not be the port for you. But if you want Quake exactly as it felt in the '90s, you're in the right place..."
Minor fixes regarding e-uae-sdl2 (version for QEMU to work with “compositing” where emulation with sm502 works very fast). Many thanks to @LiveForIt for working on e-uae!!! Thanks again for the fixes regarding accelerator.library and bsdsocket.library.
I don't know the people who worked on JIT[ and the entire e-uae emulation under PPC )to thank them, but I would also like to thank them and apologize for not mentioning them.
*) If no one is interested, I apologize for the spam. I am posting my videos to show that someone still has “childlike joy” from AOS4
@Maijestro @Djk83 - thank you for your kind words I am currently undergoing a small revolution, switching completely to ARM. My x86_64 broke down and I have no intention of repairing it. My old machine for the AOS4 hardware project, which cost €35 for x86_64 for PCI passthrough, still works for me, but it's only used to run AOS4 and nothing else. I have a backup of all data related to compilation and programs for AOS4, but... I have wanted to get rid of x86_64 for a long time and now seems like the best time I bought a new Mac M4 (memory prices are rising and I don't know how much Apple will raise prices in its annual calculations), and my Mac mini m1 will be used to install Asahi Linux. I need to rebuild things for ARM on the new system to compile something for AOS4. AOS4 is just a hobby, so first I need to build my environment for Linux ARM. Linux is my primary system, along with MacOS.
Does SDL2/3 already support VAAPI on OS4? I'm just asking because I've run into major issues; I've been trying to port FFPlay with the VAAPI SDK for a while now, but everything I've tried has failed.
A new renderer for Vulkan might also be cool; the Vulkan OS4 SDK is available in the OS4Depot.
Thanks anyway for your tireless work on SDL2/3.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
Hello everyone, I'm new to the forum but not to the Amiga world
I'm currently trying to port an SDL2 project on AOS4 but I'm having some linking problems after I've updated SDL2 to 2.32.10 and SDL2_mixer to 2.8.1.
I' had SDK 53.30 and before the updated it worked perfectly and I wa able to compile and link correctly my project.
I've tryied to upgrade the SDK to 54.16 and after some linking issue with __gthread__function that I've managed to solve I'm still having issue with libSDL2.so not finding cxa__initialize routine.
@Kirirur On newer SDKs, you're using a newer version gcc/g++ Add “-athread=native” when linking. Build a static version. It's safer. Not every AOS4 user may have the latest version of SDL2 (.so). Skip reading FLAGS from “pkg-config”. From what I can see, your project doesn’t use SDL2_mixer. Remove all unnecessary dependencies on SDL2_mixer on line 19. Add only -lSDL2 I hope everything compiles for you now...
You may also need to add the source files to the `include` directory and the library to the `Makefile.aos4` if they aren't exported and visible to the compiler. EDIT: A lesson learnt for me – don’t write anything you haven’t been able to check. Of course, it uses SDL2_mixer. For me, it compiles correctly statically with gcc-11 after adding ‘-athread=native’ screen- > https://ibb.co/9jDj5jp
Edited by smarkusg on 2026/6/2 13:46:58 Edited by smarkusg on 2026/6/2 13:55:49
Thank you for your hint, I've already added the flag -athread=native to my working copy of the makefile; with that all the "__gthread_xxx unresolved reference" are gone but remained the "__cxa_initialize" claimed by libSDL2.so.
I will try to static link the libraries (indeed my project is using SDL2_mixer ).
Execuse me: with the EDIT you meant that with gcc 11 (currently I'm stiking with the default 8.4) you managed to compile with dynamic link?
EDIT: Ps. if you want to take a look to the complete project, you need also to checkout the "data" repository Unfortunately when I started the project I tought keeping data and sources separated was a good idea.
Execuse me: with the EDIT you meant that with gcc 11 (currently I'm stiking with the default 8.4) you managed to compile with dynamic link?
Yes, I compiled it for testing. Everything went smoothly. I haven't run this build yet.
I don't know if you're compiling the code natively or via cross-compilation. For native compilation, an add-on containing gcc 11.5 has been released -> https://github.com/AmigaLabs/SDK-Addon/releases/tag/1.5.0 I think the problem you described isn’t an SDL issue. I’ll check the executable file with the necessary files tomorrow and let you know via private message.
Thank you again! I'm currently using FS-UAE 3.2.20 with Amiga OS 4.1 FE Update 3 to develop and test my application. I setup my environment some years ago, when the available SDK version was 53.30. I just recently become aware of some more recent version of both SDL ecosystem and SDK (thank you very much for the github link).
Being far from the Amiga environment for a long time I am not currently fully aware of the right channels to read/monitor to stay up to date.
Ok, so now I will try to update my environment with the suggested package and I will let you know if I had success.
EDIT update: ok, I've downloaded and installed the SDK Addon, I've selected gcc 11.5, added the flag -athread=native but unfortunately nothing changed: csx_initialize is still unreferenced. The SDL2 environment has been downloaded from OS4Depot.
Edited by Kirirur on 2026/6/3 13:59:01 Edited by Kirirur on 2026/6/3 14:00:01