ToME 2 maintenance

[darwin]

So, 2.4 is using a multi-terminal set up like TomeNET now? If I download and compiled it (is it really released yet?), could I still run it in one terminal, or the console, if I wanted to?

[AnonymousHero]

So, 2.4 is using a multi-terminal set up like TomeNET now? If I download and compiled it (is it really released yet?), could I still run it in one terminal, or the console, if I wanted to?

Is there a 2.4? If so, I'm certainly not aware of it .

Currently my plan (which is taking too long to actually execute) is to go for graphical-only and qt5-only, i.e. all the other frontends will be removed and a brand new Qt5-based one will be implemented. This is mostly for practical reasons (lack of time and resources), but also because it may hold back really useful frontend improvements like rich color support, full Unicode support, consistent font support, built-in combat log in the main window, etc.

(The front end is coming along, but not nearly as quickly as I'd like. It is being worked on intermittently.)

[Caylin]

Hi, I've been trying to follow the directions to compile the latest version of Tome 2.3.x on windows, but whenever I follow the direction make jansson, it gives an error about an integer being unsigned. Did I do something wrong? Is jansson broken?

[darwin]

[quote="AnonymousHero"]Is there a 2.4? If so, I'm certainly not aware of it .[/quote]

You replied to someone earlier here about their post, with a screenshot of a '2.4.0' (which looks like TomeNET), on December 18, 2013.

[AnonymousHero]

Is there a 2.4? If so, I'm certainly not aware of it .

You replied to someone earlier here about their post, with a screenshot of a '2.4.0' (which looks like TomeNET), on December 18, 2013.

Oh, that's just an in-progres (note the "git" bit after the version number in the message line) version number. I guess I must have forgotten that I bumped that version. Sorry about that .

[AnonymousHero]

Hi, I've been trying to follow the directions to compile the latest version of Tome 2.3.x on windows, but whenever I follow the direction make jansson, it gives an error about an integer being unsigned. Did I do something wrong? Is jansson broken?

I'm afraid I have roughly zero experience with compiling on Windows, but it might help if you post the exact commands and error messages you're getting.

[AnonymousHero]

It appears that gitorious is being absorbed into GitLab, so I've imported the repository at:

https://gitlab.com/tome2/tome2

and plan to continue any development (such as it may be) there. Though I may decide to move to GitHub, depending on how I like/dislike GitLab. We'll see.

EDIT: Unfortunately, the timeline did not get imported, so it looks pretty empty, but you can see all the commits here: https://gitlab.com/tome2/tome2/commits/master

[Lord Estraven]

@AnonymousHero, FYI I've put in a push request on the cpp branch for a Vanilla style no-selling patch. Did some testing and it seems to work (and reduces the need to carry expensive stuff out of the dungeon).

[Lord Estraven]

Just FYI, master branch currently doesn't link on FreeBSD 10.1 (x86). ld says it can't find -ljansson, even with jansson installed. Apparently this is because FreeBSD doesn't include /usr/local/lib in linking by default, but I don't know how to include that with cmake...

[AnonymousHero]

Just FYI, master branch currently doesn't link on FreeBSD 10.1 (x86). ld says it can't find -ljansson, even with jansson installed. Apparently this is because FreeBSD doesn't include /usr/local/lib in linking by default, but I don't know how to include that with cmake...

Hm. Can you supply the output of

Code: Select all

cat CMakeCache.txt|grep JANSSON  

? (after running the initial cmake command).

[Lord Estraven]

The 'cat' invocation there is not needed.

Code: Select all

JANSSON_CFLAGS:INTERNAL=-I/usr/local/include
JANSSON_CFLAGS_I:INTERNAL=
JANSSON_CFLAGS_OTHER:INTERNAL=
JANSSON_FOUND:INTERNAL=1
JANSSON_INCLUDEDIR:INTERNAL=/usr/local/include
JANSSON_INCLUDE_DIRS:INTERNAL=/usr/local/include
JANSSON_LDFLAGS:INTERNAL=-L/usr/local/lib;-ljansson
JANSSON_LDFLAGS_OTHER:INTERNAL=
JANSSON_LIBDIR:INTERNAL=/usr/local/lib
JANSSON_LIBRARIES:INTERNAL=jansson
JANSSON_LIBRARY_DIRS:INTERNAL=/usr/local/lib
JANSSON_LIBS:INTERNAL=
JANSSON_LIBS_L:INTERNAL=
JANSSON_LIBS_OTHER:INTERNAL=
JANSSON_LIBS_PATHS:INTERNAL=
JANSSON_PREFIX:INTERNAL=/usr/local
JANSSON_STATIC_CFLAGS:INTERNAL=-I/usr/local/include
JANSSON_STATIC_CFLAGS_I:INTERNAL=
JANSSON_STATIC_CFLAGS_OTHER:INTERNAL=
JANSSON_STATIC_INCLUDE_DIRS:INTERNAL=/usr/local/include
JANSSON_STATIC_LDFLAGS:INTERNAL=-L/usr/local/lib;-ljansson
JANSSON_STATIC_LDFLAGS_OTHER:INTERNAL=
JANSSON_STATIC_LIBDIR:INTERNAL=
JANSSON_STATIC_LIBRARIES:INTERNAL=jansson
JANSSON_STATIC_LIBRARY_DIRS:INTERNAL=/usr/local/lib
JANSSON_STATIC_LIBS:INTERNAL=
JANSSON_STATIC_LIBS_L:INTERNAL=
JANSSON_STATIC_LIBS_OTHER:INTERNAL=
JANSSON_STATIC_LIBS_PATHS:INTERNAL=
JANSSON_VERSION:INTERNAL=2.7
JANSSON_jansson_INCLUDEDIR:INTERNAL=
JANSSON_jansson_LIBDIR:INTERNAL=
JANSSON_jansson_PREFIX:INTERNAL=
JANSSON_jansson_VERSION:INTERNAL=
__pkg_config_checked_JANSSON:INTERNAL=1

[AnonymousHero]

The 'cat' invocation there is not needed.
(snip code)

Heh, old force of habit. (It's sometimes easier to start with a cat when you might be going to rearrange the pipeline later.)

Anyway, could you try adding the line

Code: Select all

  LINK_DIRECTORIES(${JANSSON_LIBRARY_DIRS})

inside the IF(JANSSON_FOUND) block and see if that helps?

[Lord Estraven]

That worked. Thanks!

(Though linking it took over 30 seconds, hung my workstation's sound output twice, and produced a much larger binary than on Linux. The workstation has 8 GB of RAM and a 3.5 GHz dual core processor... Le sigh.)

[AnonymousHero]

That worked. Thanks!

Great, I'll add that to a push I'm (probably) doing later today.

(Though linking it took over 30 seconds, hung my workstation's sound output twice, and produced a much larger binary than on Linux. The workstation has 8 GB of RAM and a 3.5 GHz dual core processor... Le sigh.)

Sounds strange. I'm pretty sure it shouldn't take that much memory to link, but it sounds like linking might have caused excessive swapping...

[Lord Estraven]

It wasn't swapping; my guess is a scheduling or driver issue. For all that FreeBSD does sound mixing in kernel space, it seems to have problems with sound skipping under load. This also happens during heavy disk I/O, e.g. when installing stuff in Virtualbox.

Happens on my workstation. Not on my laptop. No hints in dmesg or anything. I very much doubt it's curable, especially seeing as the workstation is a relatively recent custom machine; vs. my fleet of laptops, which were all built circa 2007.

(And FreeBSD is a great OS in a lot of respects, but still playing catch-up to Linux in some areas. The problem is compounded by the old licensing incompatibility with Linux kernel code.)