Bug#775406: wolf4sdl should be a wrapper script that runs the right engine

[Fabian Greffrath]

Am Donnerstag, den 15.01.2015, 10:51 +0000 schrieb Simon McVittie: 
> It seems non-ideal that the user of wolf4sdl is expected to know
> which engine they should run. If wolf4sdl was a script rather than an
> alternative, it could look at available data and decide which one to run:

Good idea! Should be pretty straightforward to implement.

> (Of course, it would be even better if the upstream code could
> detect this at runtime rather than needing to be recompiled with
> different #defines, but I realise that probably isn't going to happen.)

Unfortunately not. Upstream is dead for a few years and the code paths
diverge quite a bit depending on the set of compiler flags (e.g the
#ifdefs are spread across enum{}s and different headers are included,
etc.), so I am not going to start this effort on my own. :(

Cheers,

Fabian