[hatari-devel] Crosscompiling Hatari for GP2X Wiz

[Matthias Arndt]

Am Dienstag, den 29.03.2011, 00:16 +0300 schrieb Eero Tamminen:
> Hi,
> 
> On maanantai 28 maaliskuu 2011, Thomas Huth wrote:
> > schrieb Matthias Arndt <marndt at asmsoftware.de>:
> > > /home/marndt/src/hatari/src/resolution.c:46: error: 'SDL_VideoInfo'
> > > has no member named 'current_w'
> > > /home/marndt/src/hatari/src/resolution.c:46: error: 'SDL_VideoInfo'
> > > has no member named 'current_h'
> > > make[2]: *** [src/CMakeFiles/hatari.dir/resolution.c.o] Fehler 1
> > > make[2]: Verlasse Verzeichnis '/home/marndt/src/hatari/wiz' make[1]:
> > > *** [src/CMakeFiles/hatari.dir/all] Fehler 2 make: *** [all] Fehler 2
> > > make[1]: Verlasse Verzeichnis '/home/marndt/src/hatari/wiz'
> > > 
> > > 
> > > My libSDL for the target is not the latest version and probably it is
> > > unlikely to get one.
> > > For compatibility reasons this obvious new call of SDL_ should be made
> > > optional or replaced with backward compatible code.
> > 
> > According to http://sdl.beuc.net/sdl.wiki/SDL_VideoInfo the fields
> > current_w and current_h have just been introduced with SDL 1.2.10 ...
> > Eero, could you please put some proper #ifdefs here?
> 
> That's a really ancient version of SDL.  I would suggest using Hatari v1.4
> or older if one needs to build against older SDL version.  Older versions
> of Hatari are faster too...

There might be targets where you cannot simply build a new version
because setting up th crosscompilation is difficult (as we se above) and
not always straightforward.

> Building a bit newer version of SDL too is what I would recommend though
> because the screen size checks Hatari now does are kind of important to
> prevent Hatari ending up with too large screen settings and aborting on
> every startup because of that...

It is sad that you fulfill my expectations. Your code is the best and
all other setups are not valid or outdated or whatever excuse you post
here. 

What is so difficult to think about backward compatibility or making
code parts OPTIONAL at compile time?

Stop applying the Java "no code has to be optional" approach to portable
C sources!

Guess I have to do a fork then for my personal purposes.

Matthias
-- 
Matthias Arndt <marndt at asmsoftware.de>
PGP-Key: http://www.final-memory.org/files/marndt.asc   ICQ: 40358321
>>> Jabber: simonsunnyboy at jabber.ccc.de <<<