Is standalone Reicast using SDL1.2 or SDL2?

hissingshark

Hi,

I'm currently migrating my Retropie setup from an RPi3 to a Vero4K running OSMC. This is an Amlogic S905x SOC, which in common with the RPi3 runs an ARM cortex-53.

I have standalone Reicast from master built and running on the Vero4K and performance is reassuringly improved upon the RPi3. However I have noticed a few issues that didn't exist before. Specifically:

The exit button is different to the one configured to (I set SELECT and got LEFT_ANALOG_STICK - at least there is one);
the rend.widescreen option in emu.cfg is ignored (the emulator can do it though - I edited the source and set the widescreen flag to permanently true and it worked ok);
Playing Ikaruga there are sections of the first level where no baddies appear where they should, then after that they come as usual but the controls are unresponsive and their bullets do no damage. The game coasts along and then returns to normal at the next level...

I'm trying to find what is done differently and I see:

It is a different SOC/GPU even if the CPU is the same (can't help that);
The Retropie source version is older (I have tried to build this version but it didn't help any of the glitches);
? which SDL version used.

My builds have used SDL2.
Retropie has module scripts for SDL1.2 and SDL2.
The module script for Reicast requires libSDL1.2-dev as a dependancy, yet the Makefile for Reicast only uses sdl2-config.

So any ideas which version is used?

Many thanks,

hissingshark

Does anyone have an idea? SDL1.2 or SDL2 for Reicast?

Actually, @BuZz would this have been your work?
Failing that idea, what was the age/commit of the binary so I could try and rebuild from that era?

hissingshark

It gets a bit weirder.

Despite libSDL1.2-dev being a dependancy the Makefile actually doesn't use USE_SDL=1 so it's built without it anyway! So much for my original question.

I've tried using the "update from source" option in Retropie-Setup and the newer version it builds is buggy in a similar way to my Vero4K builds. I guess the Reicast devs have a commit somewhere that's broken it a bit. So again it would be very useful to know when the Reicast binary was built? so I can pull from that time to compare.

Incidentally if the Retropie devs are reading this there is a Reicast commit "6ae93b3" which breaks it to the point of segfaulting at startup. This affected the the Vero4K and as it shares a CPU with the RPi3 it will likely break on their too, so be aware should you pull in anything newer from their repository.