Late last year I went to the Ordnance Survey to see a demonstration of their new OpenSpace mapping service. It was there that I met Artem Pavlenko, who wrote Mapnik. We talked briefly about a few things, one of which was the Boost C++ libraries. I suggested that using such libraries makes software harder to build and install... "Oh no," he said, "Boost's all in the header files, so there are no library dependency problems."

Well that turned out to be a big fat lie.

I've just been trying to build Mapnik on my stock Debian Etch box. Mapnik's build system couldn't find the required Boost libraries on its own, and it wasn't possible to just tell it where they were...

Checking for C++ library boost_filesystem-mt... no
Could not find header or shared library for boost filesystem, exiting!

Mapnik doesn't use makefiles or Autoconf - instead it uses "Scons", a build system written in Python. Now, I love Python, but it's not the solution to every problem. It's hard to write makefiles that work on a wide variety of platforms. Autoconf largely solves that problem, but it too is hard to learn and use. Using C++ makes for even more problems. That's tough - it simply is a hard problem. If you want to make a cross platform source distribution, you will have to work at it.

Scons seems to be an immature tool, that simply doesn't solve half the problems that Autoconf does. It's probably easy to use, but why bother if it doesn't deliver the goods either. It's pretty easy to write a plain makefile that compiles the code on your chosen OS. If you can't be bothered to go through the pain of making it cross platform (and I don't blame you), then don't use something half-arsed like Scons - that just makes everyone's life harder.

Anyway, rant over. I eventually got Mapnik to build on Debian Etch by adding symbolic links, with the names Scons expected to see:

mkdir -p /usr/local/lib
cd /usr/lib
`ls libboost*.so | grep -v -- '-gcc-' | sed 's%\(.*\)[.]so%ln -s /usr/lib/& /usr/local/lib/\; %'`
echo /usr/local/lib > /etc/