It's just cmake. There's nothing special. I got it up and running last year on debian, spoke to jean-paul, and submitted patches, which were accepted.

 

Now, yes, boost is a bitch on steroids, the people who created it should be castrated or something suitably painful as a way to reflect the level of pain that they've inflicted on others through their thoughtless lack of proper strategic planning on API changes.  I believe I have had up to EIGHT f**bbn versions of libboost simultaneously installed at some point. Absolute insanity.

Anyway.

If i recall correctly I set up a debian/stable chroot in order to get out of the hell that is boost.

The normal way that this is dealt with in debian is to use the auto-chroot-build debian developer tools. This guarantees a consistent clean environment. I forget the name of the tool, so did the chroot manually.

The patches that I added were down to strange spurious changes to the linker phase of upstream cmake or dependencies.  Cant recall the details but I had to list all of the libraries manually even those that had aleady been linked in to other shared libraries.

On ubuntu they allow shared libraries to recursively pull in their dependent shared libraries into the executable being linked.

It was a pain in the ass to track down, but should be fine, now.

L.