mapnik
Debug version of mapnik.dll and all dependencies
This would be a huge amount of effort - as it would require a parallel rebuild of the whole stack, but in debug mode. While desirable, hard to know if I will ever have time to pull this off
When you find some time to work on the full debug windows version, would it be possible to add the config in the boost-build files for the debug-python variant? I have built myself a debug version of mapnik that uses the debug version of boost python that uses the debug version of python The boost dlls must be compiled with --python-debugging=on,k and get a name like boost_python-xxx_xxx_gyd.dll instead of boost_python-xx-xx-gd.dll To be able to link mapnik to that, i had to build with variant=debug-python instead of variant=debug, but still got a few errors, because no config was set for this variant.
I think i managed a correct build with the following commands :
sed -i -e "s/
-e "s/-gd-/-gyd-/"
boost-build/site-config.jam
sed -i -e "s/
This simply renames all lines pertaining the debug variant so that they are used for the debug-python variant, and modify the changed part of the name of the boost libraries to link with. So i think a manual copy/paste of the lines for debug to debug-variant and modification of the boost libs name for this variant would make the configuration work from scratch
@bartoli - thanks for the details. I've not given any thought to this yet and I'm sure I would hit this so thanks for commenting. Please post back if you needed any other customizations to get things working in debug. Did you use the scripts contained in this repo/readme for building mapnik dependencies too?
No, i built them with my own build environment, and mapnik with v2.2 and mapnick-packaging of the same date, with direct calls to bjam (and modifs here and there to set correct paths/versions/filenames/options for my environment).