[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Adonthell-devel] Adonthell compilation report

From: Kai Sterker
Subject: Re: [Adonthell-devel] Adonthell compilation report
Date: Fri, 4 Jul 2008 10:28:56 +0200

On Fri, Jul 4, 2008 at 7:40 AM, Julien Laumonier <address@hidden> wrote:

> Hi,
> After many nights, i have just succeed in making worldtest to work with
> graphics and without segfault. Here is my remarks. I've compiled adonthell
> cvs with gcc 4.3.1 and cmake on an x86_64 architecture.
> 1) There was only one problem in the map_view.h file. I think because of the
> new organization in the standard header files in gcc 4.3, I had this error :

This is one thing where we probably need to invest some resources, but
I'm not sure if now is the right time. The biggest issue here is
certainly the deprecation of hash_map in anticipation of the upcoming
C++0x standard. There is already a central place where we could deal
with that (base/hash_map.h), but as long as the current GCC
implementation of C++0x is not ready for production, it's probably
better to wait.

> It seems that adding "#include <cstdlib>" in map_view.h resolves the
> problem.

I'll add that then.

> 2) I am a complete newbie in python and maybe i missed something but after
> the installation (make install), the python search path was not updated with
> the adonthell installation directory
> '/usr/local/lib/python2.5/site-packages'. I had to add it manually using the
> environment variable PYTHONPATH. Is there another way (automatic ?) to do
> this ?

Hm ... this is a little odd, as the Python modules should be installed
in the site-packages of your actual Python installation. Then they are
found without any additional help of the user. I assume your Python
installation is in /usr, not in /usr/local? Sounds like a problem with
the build system, if it does not detect this correctly. You're using
cmake, right?

> Hope this help to improve adonthell.

It certainly does. The more different systems we can test on now, the
more painless installation will be for future users.

> After that, i'll try to understand the
> code structure and try to modify some stuff.

Great. If there are questions, please let me know.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]