ToME: the Tales of Maj'Eyal

I'd love to get ToME under the GPL -- and will hereby state publicly that all my T2 code is dual-licensed under the GPL and the T2/Angband license. (I should really get around to add that in the code...)

DarkGod has indicated (at least to me, via PM when I asked about it, nor sure if there's a public thread anywhere about it -- he may have posted before the Great Forum Crash (in which case it's gone). I'm sure we could convince him to announce it again publicly if necessary.

However, there's a lot of code by a lot of authors. Much of the code could perhaps reasonably be assumed to be licensable under GPL as part of the Angband GPL effort, but this is kind of grey area -- it's not clear to me whether the relicensing in that case was a general "sure, use my Angband (specific version) code under GPL" or "sure, use my Angband (any version) code under GPL".

I'm sure Neil Stevens would also need to give his permission. Not sure if he's around on these forums. I also think Furiosity may have to give permission since the integration of Theme into ToME -- a substantial bit of Theme code was moved to C. I took the license in the Furiosty code to be equivalent to the T2/Angband license.)

I guess a major first step would be in finding out who needs to be contacted and if they have been contacted as part of the relicensing effort for Angband -- I imagine this would involve going through the "credits.txt" file and then going through copyright headers in *.c files. I'm pretty sure that effort must have been documented, but I have no idea where.

Finally, we are only talking about relicensing

I noticed the TOME binary is in not in /usr/games, but /usr/games/bin, which will not automatically run on most systems. I see I never added it to /etc/profile, so I assume this is another change. Is it ok if I make a package install the binary in /usr/games?

darwin wrote:I noticed the TOME binary is in not in /usr/games, but /usr/games/bin, which will not automatically run on most systems. I see I never added it to /etc/profile, so I assume this is another change. Is it ok if I make a package install the binary in /usr/games?

I don't see any particular problem in installing the binary itself to /usr/games (though I don't see the value of using that particular directory -- whatever floats your boat). As long as the CMAKE_INSTALL_PREFIX is set correctly and the library files are installed to ${CMAKE_INSTALL_PREFIX}/lib/tome, you shouldn't have any problems.

[quote="AnonymousHero"]I don't see any particular problem in installing the binary itself to /usr/games (though I don't see the value of using that particular directory -- whatever floats your boat). As long as the CMAKE_INSTALL_PREFIX is set correctly and the library files are installed to ${CMAKE_INSTALL_PREFIX}/lib/tome, you shouldn't have any problems.[/quote]

Also, /usr/games is traditionally used just for game binaries. There are many other directories used for other files games use, like /usr/lib/games, /usr/share/games, /usr/var/games. I feel that putting a directory in my /usr/games utterly ruins my system layout.

Sooo... Has anyone managed to get the git master compiled and running on Windows? If so, can you describe how you did it?

And what about on OSX (presumably via the SDL interface)?

Mind, I have little working knowledge of Windows and none of OSX, but most players in T2's hypothetical future will be on one or the other of those two...

Okay, I have managed to get halfway with Windows... I think.

Procedure looks like this:

1. Install msysgit (the dev version with MinGW) to somewhere accessible by your user.

2. Install CMake. Add it to PATH (for your user or everyone).

3. Download jansson. Unpack it somewhere, then ./configure, make, and make install.

4. Download and unpack pkg-config. Export CFLAGS="$CFLAGS -march=i486" and run ./configure with --with-internal-glib. Run make and make install.

You now have all the deps for a Win32 build. In theory, you should be able to enter the T2 build directory, run cmake -G "MSYS Makefiles", and then run make...

But in practice pkg-config will fail to find jansson, even though the .pc file for it is in the right place. Not sure why this is.

I'll keep working on it, when I've got the spare time (and when I'm in the mood to pick a fight with a bad OS).

Sounds very promising.

I wonder if we should do a "vendor" import directory where the source of all dependencies is included and could be compiled as static libraries (in place) and included that way. This is a bit of an annoyance for packagers and from a security standpoint, but it might make it easier on Win32. (We could perhaps make this conditional on WIN32.)

Umm, we have a problem on the Linux front...
Needless to say libjansson.so.4 is in the library path, and the whole thing compiled fine. Just to make sure I hadn't messed up with Stow, I tried removing jansson and reinstalling it with Slacktrack... No luck whatsoever.

Any idea what commit might have caused this, before I start bisecting? Assuming it's not my fault anyway.

Edit: duh, me stupid. You have you run ldconfig after installing a new library manually. Double duh.

Does anyone have a windows 7 compatible version of TOME 2.3.X? I tried the floor tile bug fix and it worked great for a bit. Now TOME (even when I reinstall) doesn't work. It'll open the three windows as always, but they are blank. Hitting any key a few times will close the program. TOME 2.3.X is one of my favorite games ever. Please help!

FatGuyLittleCoat wrote:Does anyone have a windows 7 compatible version of TOME 2.3.X? I tried the floor tile bug fix and it worked great for a bit. Now TOME (even when I reinstall) doesn't work. It'll open the three windows as always, but they are blank. Hitting any key a few times will close the program. TOME 2.3.X is one of my favorite games ever. Please help!

Can you access the drop-down menus at the top of the main menu? Try changing the window font.

Thanks!

I rebooted the system and it seems to be working again.

FatGuyLittleCoat: were you able to get 2.3.10 compiled on Windows? Because if so that would be great, and I'd love to hear how you managed it.

Is ToME-ah developed for 64-bit only? I made a SlackBuild for v2.3.10-ah and it was refused by the SlackBuilds team because it would not compile under a 32-bit system.

darwin wrote:Is ToME-ah developed for 64-bit only?

Not as a matter of principle, no. In practice it isn't compiled for 32-bit very often, so things may slip through. (Particularly format strings and such.)

darwin wrote: I made a SlackBuild for v2.3.10-ah and it was refused by the SlackBuilds team because it would not compile under a 32-bit system.

If you can get the error messages and post them, I'd be grateful. (I don't have much time, if any, to devote to ToME 2.x at the moment, but I'll get around to it when I can.)

Oops, sorry, there was not a problem with ToME compiling on 32-bit. It was Mangband, which I forgot about, then was thinking more about ToME, which I just made some errors in the build script for. However, I had the following problem. The main part of my SlackBuild is below.
This is what happened (everything seemed to compile, then there was a linker error.)