Hello, It seems to me also that there should be some more iterations or some more relevant documentation. I would feel more comfortable using submodules, but without them my best attempt up to now is (ublas as an example here): git clone https://github.com/boostorg/boost modular-boost cd modular-boost {manually relpace /v2 with /buildv2 in boost-build.jam and bootstrap.sh} cd tools git clone https://github.com/boostorg/build cd .. ./bootstrap.sh cd libs/numeric git clone https://github.com/boostorg/ublas cd ../../ ./b2 include=libs/numeric/ublas/include libs/numeric/ublas/bench1 (to compile bench1 for example) This relies on the assumption that the rest of boost is in an accessible location in the system. -Nasos On 05/09/2013 10:40 AM, Beman Dawes wrote:
On Thu, May 9, 2013 at 9:46 AM, Bjørn Roald
wrote: On Thu, 2013-05-09 at 07:43 -0400, Beman Dawes wrote:
2) The procedures described in https://svn.boost.org/trac/boost/wiki/TryModBoost need to be updated, the dependency on CMake needs to be removed, and the procedures need to work. I tried to check this out, I think Steven Watanabe did some test with a modification to b2 to automate this. So my intention was to look for it and possibly try it or ping Steven.
However trying the steps posted on the wiki seems to fail on the
git submodule update --init
step.
There is no .gitmodules file in the top directory modular-boost master branch HEAD, so I guess there is no way git submodule know what and where to fetch from. It silently completes as there is nothing to do. There must be something that is disconnected here. Yes, and that's part of why I'm concerned. The modularization of the individual libraries is now working nicely with full history for all branches, but the modular-boost master hasn't been handling submodules for quite a while now.
--Beman
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost