On 30 Nov 2014 at 10:00, Rene Rivera wrote:
Hasn't there been lots of discussions of the difficulty of having libraries other than directly under boost/libs ?
There were some teething problems, but haven't those all been resolved?
There is one "problem" I ran into that as a result of that I suggested/requested that we put all submodules at the boost/libs level. I attempted to create a minimal subset of Boost to just build the documentation tools < https://github.com/grafikrobot/boost-doctools/tree/develop>. And it was hard to find and recreate the structure of sub-sub-modules as it wasn't obvious where they mapped from the build errors. And in some circumstances there where duplicate names at multiple levels which made it harder.
There is also a problem in the future when Boost library A may depend on v1 of submodule X while Boost library B may depend on v2 of a submodule X. I don't think the solution BindLib requires which is that each Boost module mounts its dependency submodules inside itself (probably the include directory) is avoidable. At least with per Boost module submodules, they can pin themselves to some commit SHA. It would be nice though if Build could spot the same commit SHA link in a git submodule and simply symlink it rather than checking out another copy. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/