tl;dr ..
I've got pnds for Hatari 1.3.1, 1.4.0, 1.5.0 and not yet for 1.6.1. Did a fresh build of 1.5.0 today and just doing a test now .. 1.6.1 is annoying with its cmake sillyness, so someone bug me in a month or so, pretty tied up now
Hrrm, my 1.5.0 build is funky .. maybe I need ot go for 1.6.1 and do the pain to get cmake cross compilation sorted out, and then at least be ready for 1.7...
No time to fix it right now, so keep bugging me, remind me on Monday
Aside geekery:
I'm an old Atari nerd and have written my own ST emus and such, I'm pretty on top of the ST emu scene
You _Really_ don't want to see the stack of Atari hardware I have and am actively hacking on
A big problem the ST emu scene has had over the years is all the closed source emus, which some went open .. ie: PacifiST was a decent one, but stayed closed; then things like the .stt file format being closed and having to be reverse engineered, yet the guys wanting it to become standard (!?!), stuff like that. WinSTon and so on went open, but all of this really drove Hatari to bnecome what it is. (STonX was pretty good early on, but went stagnant many a moon ago.)
So Hatari is the main contender in the open source ST emulation arena; some of the closed guys have opene dup, but since they were closed for so long, and only went open after being 'dead' forawhile, Hatari has made up most of the slack imho; mind you, the closed guys usually had really got cycle accurate timings and were good with demos, but Hatari is pretty good (and getting better) there, as well as having a whole pile of interesting features .. good hard drive support for a variety of virtual disk types, Falcon and TT030 emulation, remote control abilities, all sorts of great stuff.
I discontinued my own ST emu when Hatari came around, and once we got more pwoerful machines like Pandora, I stopped hacking on OutcaST/CaSTaway as well.. totally outclassed
Steven (I think he's the STeem maintainer now) is probabyl quite a capable coder, but I dont' think he's a strong Linux/Unix ghuy; I've not followed, but the vibe I saw back then was he wasnm't familiar with the particular ins and outs (ie: linux audio is historically a big mess, trips up a lot of people
; Steem looks like a not too hard port though, so it may be worth doing as another alternative .. but for my part, I rather prefer Hatari so stick there .. only have so much free time lately :/ (got 3 kids now, how thje heck did _that_ happen
(If you're curious, I use Hatari on Pandora to run TOS-ports of gcc and so forth, to build Falcon-compatible apps, and then run them in Hatari and some real Atari hardware. Pandora ftw
Hatari switched (unfortuantely imho) to cmake build system from traditional make/autotools, and I really dislike cmake (at least for cross compilation setups); few maintainers know how to set cmake configs up (the Hatari guys..) so cmake usualyl doesn't work out of the box, and you need to futz with a few dozen files just in the build system; I prefer to spend my time on the actual code.. and stuff like Makefiles/autoconf are goofy, but well known and simple to screw with. Anyway, so I use some old config hacks I made earlier in Hatari history, so I can build up to Hatari 1.50 without too much trouble. Hatari 1.6.0 is broken (lots of bufs), but 1.6.1 is pretty good .. but its changed enough where I need to re-figure out how to build it . .the cmake stuff is just a big ugly mess there imho. Probably not too ba to fix, but its a half day I'd rather not do right now, got not enough time and too many things I want to work on