We keep getting segfaults that don't reproduce the second time it
is run, so maybe this will catch them.
It also moves the test execution code out into a script.
If we try to send a message immediately after signaling SIGHUP to
wesnothd, it won't get caught by wesnothd, probably because the control
socket is being reopened just as the message arrives. Thus, we need a 1
second delay after the signal.
This was fixed in production a while ago but I forgot to commit the
change.
At least on baldras' version of screen, the stuff command argument here
absolutely needs to be wrapped in single or double quotes to work.
I actually fixed this months ago but forgot to commit.
* Using scons -Y to point scons to a source tree that might be
read-only for the user building campaignd/wesnothd (as is the case on
baldras).
* Renamed or changed several variables for clarity.
* As a side-effect, links within the server instance dir are now
absolute rather than relative (/home/wesnoth/build/foo/bar instead of
../../build/foo/bar).
* ~/builds-int/<version> is the intermediate build directory
* ~/builds/<build-id> remains as the target directory
* /usr/src/wesnoth is the source directory base (we need to handle
basilic and gonzo separately later)
I'm fairly sure nobody other than me could possibly demand a more
detailed description of this commit.
They mostly seem to be code cleanups or style changes, plus the hack to
try to start the irc echo for the old instance after restarting... which
doesn't seem to be working.
* Added code for handling 1.8 and 1.10
* Don't use libana for Wesnoth versions that include it (1.9.x)
* We now use Git, not SVN. The downstream repository is managed
externally, so we need to update a git-new-workdir checkout every
time we want to build.
* Other nondescript changes
(Apologies for the horrible commit message, but it looks like there was
more than my own changes awaiting to be committed.)
I wrote this a long time ago and have been using it to ease testing of
Wesnoth's default configuration under different conditions ever since.
It creates a new configuration and data directory under /tmp that only
exists for the duration of the Wesnoth session, and disables WML cache
functionality.
This is extremely useful for quickly testing and debugging functionality
dependant on user configuration settings.
