Houdini ships with a fixed version of Boost it uses, and the symbols are unaltered. If you rely on boost to a serious extent (e.g. can't use C++11 and therefore need Boost for things like smart pointers, counting etc.), then you either have to use the same version, and link against the existing Houdini deployment (excessive reliance on a client as a root dependency), or you have to re-cook your own boost with alternate symbols (and building boost with symbols switch is... unpleasant) just so you can use Houdini elsewhere.
For a lot a lot of places it's a non-issue, not everybody has a backbone of the extent and pervasiveness where this is an issue. For some places it's a tolerable issues, as they are OK requiring H as a root element as that stretch of pipe might be well isolated. For some other places it's a gigantic pain in the butt :) SESI is aware and will, I'm sure, eventually wiggle its way out of the issue, and when C++11 will be more widely supported, which is next year, a lot of Boost can be replaced with native primitives and stdlibs items. For now, you either compartmentalize, or push your RnD guys through groan inducing deployment pains :) On Thu, Sep 11, 2014 at 5:18 PM, Jordi Bares <[email protected]> wrote: > > > > I would love to know more about the Boost dependencies being an issue as I > am not familiar with it.ur users will know fear and cower before our > software! Ship it! Ship it and let them flee like the dogs they are! >
