Two remarks :
- the Linux binary won't run in the latest Ubuntu (10.04 Lucid). It causes a segmentation fault. Compiling from source works perfectly, though. (In fact this was the same in beta 1 and beta2 but I wasn't really posting on the forums yet at that time.)
- it's possible to load old games (from beta2), but they don't really work : impossible to read the 'i'nventory, the 'C'haracter description and old areas don't seem to behave as they should.
As a general rule, do not expect beta savefiles to keep compatible
As for the linux binaries yes they are annoying to do :/
[tome] joylove: You can't just release an expansion like one would release a Kraken XD
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning
As a side note, what the hell do I do with my beta2 chars? I can't play them anymore (loading a beta2 char works but the game hangs forever after that) and can't delete them.
Ah yes I must add a delete savefile option
until then jsut delete them manually in home/T-Engine/4.0/tome/save/ or just create a new character with the same name
[tome] joylove: You can't just release an expansion like one would release a Kraken XD
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning
As dg said. To clarify, C:\Documents and Settings\<Username>\T-Engine\4.0\tome\save is the default under XP; it took me a C: drive search to figure out what exactly home was, heh. Reeeaaallly wish that could be modified (easily, heh), by the by.
My side note: What madness has been inflicted upon the trollshaws!? That place is a navigational wreck all of a sudden. Fortunately, the Old Forest is still sane and shift-run-able (pleaseohgodsdon'tchangethat). Even less reason to bother with the first two dungeons, now...
Well, the shaws are prettier, I'll give it that. Just hell to play in, heh.
Frumple wrote:My side note: What madness has been inflicted upon the trollshaws!? That place is a navigational wreck all of a sudden. Fortunately, the Old Forest is still sane and shift-run-able (pleaseohgodsdon'tchangethat). Even less reason to bother with the first two dungeons, now...
Well, the shaws are prettier, I'll give it that. Just hell to play in, heh.
Oh aye, it works, but I don't like using the mouse when I can avoid it/at all, at least when pretty much all the interface is controlled via keyboard. Dunnit help I'm on a laptop, heh.
Maybe there's room for a button to press in look mode that functions similarly?
[tome] joylove: You can't just release an expansion like one would release a Kraken XD
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning
Oh I can compile them just fine it's making them portable that is causing problem
[tome] joylove: You can't just release an expansion like one would release a Kraken XD
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning
Yes, distributions can be very different from each other - in fact, that's supposed to be a good thing. Anyway, when things become more stable, it would probably make more sense to actually build packages for mainstream distributions (.deb or .rpm) that check for required libraries first. I could do that for the *ubuntu family. Just out of curiosity, what linux distro are you using to compile the binaries you post?
[tome] joylove: You can't just release an expansion like one would release a Kraken XD
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning
Oh, ok, then that makes sense : in gentoo you're supposed to ("auto-magically") build everything from source locally anyway, but the resulting binaries are not very portable.
If you're building Linux binaries for distribution, you want to build them on the *oldest* distributions you can get hold of (and get them to build on). Programs built on older releases will often work on newer releases; but programs built on newer releases generally won't run at all on older releases.
Of course, backward compatibility doesn't *always* work either... but that's why most Linux users will probably build it from source anyway.
It breaks the linux way of doing things, but you could (assuming the libraries you use are licenced in a manner that allows this, BSD certainly) statically include those libraries. If they are (L)GPL'd then you could still use dynamic linking, but include in the package the versions you used to compile and test against, along with a shell script that makes the binary use them.
