ToME: the Tales of Maj'Eyal

Hi Guys

I am using Arch Linux, and recently compiled the 2.3.11-ah version of Tome.

The installation went ok, and it runs ok, but no matter what I try, I cannot get it to run with graphics.

The graphic files are there, and I have tried using X11, SDL and gtk2, and while I have the option for graphics, when I chose it, it does not show, although when I choose broad tiles, that works, but in ASCII only.

I am trying the commands

./src/tome -g
./src/tome -mx11 -g ( also -- -g)
./src/tome -msdl - g ( also -- -g)
./src/tome -mgtk2 -g ( also -- -g) (This version gives me a graphics menu, but selecting them doesn't work)

I have a working version of 2.3.5 , which I normally run with tome2 -g -- -b -n4 which is working perfectly, but can't figure out where I am going wrong.

In fact all versions of the -ah compile ok, but graphics are not working.

Can anyone provide any help or insight into the issue?

Thanks in Advance
Renfield

My first thought was "its a caps sensitive issue".
Is the path to the tiles correct?

However that was just an instinctive response, so it may be completely useless.

_________________
My feedback meter decays into coding. Give me feedback and I make mods.

I think it was removed somewhere along the way.

The long-term plan was to introduce a cross-platform interface (based on Qt or similar) which would make it easier to support and then to perhaps re-introduce tiles at that point... but that hasn't happened yet.

The linking issue was fixed in 7d8712ba5bcf8ba7837ca0c198f364fd208db354 -- according to the commit commit there was apparently a change in some distro toolchains which meant that "libm" was no longer automatically linked.

I'm not sure if the commit will cherry-pick cleanly into what you have, but regardless it's a trivial change that should be easy to do manually.

EDIT: Some of those main-sdl warnings also look a bit nasty, but as I recall the (32-bit compatible) fix for those was a little more invovled. What I recommend is to just ignore the SDL port entirely -- it's absolutely awful anyway UX-wise (IMO).