Development:Compiling: Difference between revisions
No edit summary |
→Fixing problems: added another know problem |
||
Line 47: | Line 47: | ||
== Fixing problems == | == Fixing problems == | ||
=== ImportError: No module named adonthell.world === | |||
In case you have multiple versions of Python installed, CMake can get confused. If, during the initial run of cmake you get a mix of versions like seen below, Adonthell will not work correctly. | |||
Found PythonLibs: /usr/lib/python2.4/config/libpython2.4.so | |||
-- Python has been found: | |||
-- CFLAGS : /usr/include/python2.4 | |||
-- LDFLAGS: /usr/lib/python2.4/config/libpython2.4.so | |||
-- Found PythonInterp: /usr/bin/python2.5 | |||
-- VERSION: python2.5 | |||
-- LDEXTRA: -lm;-lpthread -ldl -lutil | |||
-- SITEPKG: /usr/lib/python2.5/site-packages | |||
The only workaround for that is removing any superfluous Python installations, then running cmake again. | |||
=== debug.py not found === | === debug.py not found === |
Revision as of 12:42, 25 January 2009
After having installed all of Adonthell's Dependencies and obtained the source code from CVS you can finally compile it. Please follow the general instructions and see the hints specific to your OS if you get stuck. Refer to the instructions included with the source code for further details.
General Instructions
For all Systems, we assume a POSIX-like environment with GNU compiler and make and a shell. Where supported, you should use the CMake based build system, but we'll probably keep the GNU autotools around for some while too. In both cases, an out-of-source build is recommended.
CMake based build
Inside the adonthell directory type:
mkdir ../adonthell-build && cd ../adonthell-build cmake -DCMAKE_INSTALL_PREFIX=/usr/local ../adonthell make sudo make install
GNU Autotools based build
Inside the adonthell directory type:
./autogen.sh mkdir ../adonthell-build && cd ../adonthell-build ../adonthell/configure --prefix=/usr/local make sudo make install
Developing on GNU/Linux or *BSD
Most, if not all, dependencies should come with your distribution. Just make sure to install the corresponding development packages. In case that you require a newer version of a library or tool than comes with the distribution, you should be able to compile and install it yourself without much trouble.
In general, you should be able to use any IDE of your choice as long as it is not messing with the Makefiles. If you have a particular good setup, feel free to share the instructions.
Developing on MacOS X
Like on Linux, you can get most of the dependencies in the form of precompiled binaries, e.g. from the Fink Project. If you need an IDE, use XCode.
Most likely I will buy a new Mac once Leopard is released. Then I'll document all the required steps to get an Adonthell development environment going. (Kai)
Developing on Windows
Since Adonthell requires the GNU Compiler Collection (GCC), your best choices are either Cygwin or MinGW. In order to produce "true" Windows binaries that do not depend on the Cygwin POSIX layer (cygwin1.dll), setting up a development environment with MSYS/MinGW is recommended. A good IDE to use would be Eclipse, which is becoming supported directly by CMake.
Developing on other OS
Sorry, right now you are on your own. But if your system has a recent port of GCC and is supported by SDL, chances are pretty good that you will get Adonthell working. Please update this space if you did :-).
Fixing problems
ImportError: No module named adonthell.world
In case you have multiple versions of Python installed, CMake can get confused. If, during the initial run of cmake you get a mix of versions like seen below, Adonthell will not work correctly.
Found PythonLibs: /usr/lib/python2.4/config/libpython2.4.so -- Python has been found: -- CFLAGS : /usr/include/python2.4 -- LDFLAGS: /usr/lib/python2.4/config/libpython2.4.so -- Found PythonInterp: /usr/bin/python2.5 -- VERSION: python2.5 -- LDEXTRA: -lm;-lpthread -ldl -lutil -- SITEPKG: /usr/lib/python2.5/site-packages
The only workaround for that is removing any superfluous Python installations, then running cmake again.
debug.py not found
In case you get the error while make install, that a debug.py file cannot be found, simply
echo crap > ../adonthell/src/py-wrappers/runtime/debug.py