[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Adonthell-devel] Trouble building/running Adonthell
From: |
Kai Sterker |
Subject: |
Re: [Adonthell-devel] Trouble building/running Adonthell |
Date: |
Sun, 1 May 2011 21:05:12 +0200 |
On Sun, May 1, 2011 at 8:05 PM, James Nash <address@hidden> wrote:
I'll be around on IRC, so we might be able to figure this out in an
interactive way.
Anyway, a few notes up ahead:
You do not really need SDL 1.3. SDL 1.2 will be fine, you just won't
get hardware acceleration. But since you installed SDL 1.3 already,
where did you put it? Into /usr/local? Then you might have to copy the
contents of /usr/local/share/aclocal/ to /usr/share/aclocal, so that
autotools can pick up the macros for SDL.
With cmake, I'm not sure which version of SDL it has picked, but as
stated above, either should be fine.
The crash you are getting is not related to the configuration file. I
deleted the entire ~/.adonthell/ directory and on the first start, I
get
address@hidden:~/adonthell/adonthell-build/test$ ./worldtest -g
../../ wastesedge
I/O warning : failed to load external entity
"/home/kai/.adonthell/adonthell.xml"
E0501 20:51:44.183277 2324 configio.cc:258] config_io::read: errors
while parsing '/home/kai/.adonthell/adonthell.xml'
E0501 20:51:44.183395 2324 adonthell.cc:251] Error reading engine
configuration 'adonthell.xml'
there is no soundcard
E0501 20:51:44.874793 2324 screen.cc:132] *** info: Set internal view
to 576 x 432.
E0501 20:51:44.874858 2324 screen.cc:133] *** info: Set display size
to 1152 x 864.
and then it starts up normally.
The question is, do you have the glog stuff installed? In that case,
you might find more extensive logging under /tmp/lt-worldtest.INFO.
You can get logging to the console by adding
GLOG_logtostderr=1
in front of the worldtest invocation.
If you haven't installed glog, you'll get more logging on the console by using
GLOG_minloglevel=0
instead of the above.
If neither helps to locate the error, you'll need to give it a try in
gdb and supply the stack trace. However, I've also upgraded to Ubuntu
11.04 yesterday and everything runs fine here.
Kai