Clone this wiki locally
This page exists to discuss the best way for developers to debug Mapnik.
Currently I have these questions:
- What's the best way to get a Python build with debugging symbols? Will adding -g suffice? Is --with-pydebug needed?
- Do we need to compile the Boost libraries with debugging symbols as well?
- Is anything different for FreeBSD?
Here I try to describe my setup. I'm sure there are better ways but this works for me:
- Checkout the latest code:
git clone git://github.com/mapnik/mapnik.git mapnik_trunk
This has the advantages that
- you always have the newest version (
- you can quickly add test code and remove it again (
svn checkout .)
- you can easily create patches (
- Compile it as described in the INSTALL file provided in the root directory of the checkout. I have the following variables in my
DEBUG = True XML_DEBUG = True INPUT_PLUGINS = 'gdal,ogr,osm,postgis,raster,shape,sqlite' PREFIX = '/home/philipp/usr' PYTHON_PREFIX = '/home/philipp/usr' BOOST_INCLUDES = '/usr/include' BOOST_LIBS = '/usr/lib' BINDINGS = 'all' DEMO = True
- Download and install the Eclipse IDE for C/C++ Developers (79 MB)
- Create a new Makefile-C++-Project using the existing
mapnik_trunkpath where you have checked out the working copy.
- Create a debug configuration e.g. specifying the c++ demo application
- You can got through the program now step by step and make breakpoints. In the default behavior, Eclipse tries (and fails) to compile the project itself and ask to start anyway. Just say yes.
- If you change a file, recompile the project from the command line by just typing
- It is possible (but not necessary) to fine-tune Eclipse so that it does not try to build the project by itself and that is uses scons to do successfully do so.